Algolia offers AI-powered solutions to improve online search and discovery experiences, with tools for business teams and APIs for developers that help to improve user engagement and conversions across websites, apps, and e-commerce platforms.
$0
per month 10k search requests + 100k records
Cassandra
Score 9.0 out of 10
N/A
Cassandra is a no-SQL database from Apache.
N/A
Redis Software
Score 9.1 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
N/A
Pricing
Algolia
Apache Cassandra
Redis Software
Editions & Modules
Build
Free
per month Up to 10,000 search requests + 1 Million records
Grow Plus
Free / Pay as you go
per month 10K searches/month & 100K records included; $1.75 per extra 1K searches, $0.40 per extra 1K records
Grow
Free / Pay as you go
per month 10K search requests & 100K records included; $0.50 per extra 1K searches, $0.40 per extra 1K records
Elevate
custom
per year
Elevate
Custom
per year Custom search requests and records — volume-based discounts available
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Algolia
Cassandra
Redis Software
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
No
Yes
Premium Consulting/Integration Services
Yes
No
Yes
Entry-level Setup Fee
Optional
No setup fee
Optional
Additional Details
Pay as you go, scale instantly, or upgrade anytime for advanced features and capabilities.
Algolia got us up and running faster and more easily than if we'd managed elastic search and it's configuration by ourselves. Upfront and ongoing costs and complications/ custom implementations were removed from the equation by choosing Algolia out of the gate.
Against HBase, writes were faster. Reads not so much. Also ability to store in other formats would be good (such as objects). Compared to aerospike, does not compare. Aerospike blows it out of water.
Redis was initially in the list of competitors like Aerospike, Cassandra, MongoDB.The major point that outset all others is that it provides a number of read and writes to the database that no one can match. Another major factor is Redis really knows the basic components that …
Algolia is both well-suited to replace Shopify's out-of-the-box search and to very large sites with millions of products in their catalog. Algolia provides a specialized solution that benefits from very large R&D budgets and ongoing investment. Algolia offers a more retail- and open-design solution than competitors such as Amazon or Google search, which offer fewer options and fewer features.
Apache Cassandra is a NoSQL database and well suited where you need highly available, linearly scalable, tunable consistency and high performance across varying workloads. It has worked well for our use cases, and I shared my experiences to use it effectively at the last Cassandra summit! http://bit.ly/1Ok56TK It is a NoSQL database, finally you can tune it to be strongly consistent and successfully use it as such. However those are not usual patterns, as you negotiate on latency. It works well if you require that. If your use case needs strongly consistent environments with semantics of a relational database or if the use case needs a data warehouse, or if you need NoSQL with ACID transactions, Apache Cassandra may not be the optimum choice.
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
Users get instant feedback as they type, even with complex filters like brand, model, price range, and financing eligibility. This speed significantly improves engagement and reduces bounce.
A user searching for “Camry 2020” or even “Camary 20” still sees relevant Toyota Camry listings from 2020. This reduces friction, especially on mobile where spelling errors are common.
Algolia handles multi-faceted filters efficiently. For example, a user can filter by location, transmission type, color, or inspection status without any lag.
We fine-tune the ranking of search results based on what matters to our business—like prioritizing cars with higher margins or better availability in key cities.
We can experiment with different ranking formulas or UI variations to improve KPIs like lead conversion or time-to-first-interaction.
Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
Better integration of features (ex. synonyms feature is great but isn't respected by their re-ranking product)
Tooling to reduce spam search queries being triaged by system/logged to analytics panels
More automated summaries of analytics (ie. recommend synonyms to add, trends noticed in search volume in specific areas of site, easier ways to leverage API vs using website UI)
Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
Algolia is a great tool, we didn't have to build a custom search platform (using Elasticsearch for example) for a while. It has great flexibility and the set of libraries and SDKs make using it really easy. However, there are two major blockers for our future: - Their pricing it's still a bit hard to predict (when you are used to other kind of metrics for usage) so I really recommend to take a look at it first. - Integrating it within a CI/CD pipeline is difficult to replicate staging/development environments based on Production.
I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
Personally I find the Algolia integration not very complicated and the service super reactive. In terms of configuration, it's quite complete, at the end what matters is what we are able to index on Algolia. With rich data, the tool is amazing and a lot of things are possible.
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
Performance is always a major concern when integrating services with our client's websites. Our tests and real-world experience show that Algolia is highly performant. We have more extremely satisfied with the speed of both the search service APIs and the backend administrative and analytic interface.
It’s non existent. No tech support and no customer service… my application was blocked and is currently inactive causing huge business disruption, and I’m still waiting days later for a response to an issue which could be resolved very very quickly if only they would respond. Very poor from a company of that size
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
Algolia gives way more control for a non-developer than AWS Elasticsearch Service. Previously we'd have to have our developers make adjustments to site search relevancy, typos, prioritizing certain attributes over others, etc. but now the marketing and website team can do that themselves in the Algolia dashboard
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for web and mobile applications due to its performance concern. Cassandra, by contrast, offers the availability and performance necessary for developing highly available applications. Furthermore, the Hadoop technology stack is typically deployed in a single location, while in the big international enterprise context, we demand the feasibility for deployment across countries and continents, hence finally we are favor of Cassandra
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Overall is a scalable tool as the environment and the backend functions are the same and many things are done directly on the tool so without the need of further specific developments. However some things could be improved such as documentation for integration that could help in doing whitelabel solutions
Users who had abandoned our product (attributing slow search speeds as the reason) returned to us thanks to Algolia
We used Algolia as our product's backbone to relaunch it, making it the center of all search on our platform which paid off massively.
Considering we relaunched our product, with Aloglia functioning as its engine, we got a lot of press coverage for our highly improved search speeds.
One negative would be how important it is to read the fine print when it comes to the technical documentation. As pricing is done on the basis of records and indexes, it is not made apparent that there is a size limit for your records or how quickly these numbers can increase for any particular use case. Be very wary of these as they can quite easily exceed your allotted budget for the product.
I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
