Need advice about which tool to choose?Ask the StackShare community!


+ 1
Amazon CloudSearch

+ 1
Add tool

Algolia vs Amazon CloudSearch: What are the differences?


Markdown is a lightweight markup language that is commonly used for formatting text on websites. In this task, I will format the provided content about the key differences between Algolia and Amazon CloudSearch as Markdown code that can be used on a website.

  1. Indexing and Searching: Algolia focuses on delivering a real-time and interactive searching experience by providing instant search results as the user types. It offers advanced features like typo tolerance, faceted search, and synonyms out of the box. On the other hand, Amazon CloudSearch provides scalable search functionality with powerful indexing capabilities, making it suitable for large-scale applications that need efficient searching and filtering of structured data.

  2. Data Integration: Algolia offers easy integration with various data sources such as databases, JSON files, and custom APIs. It provides connectors for popular platforms like Shopify, Magento, and WordPress, allowing seamless data synchronization. In contrast, Amazon CloudSearch is fully managed by AWS and can directly integrate with other AWS services like Amazon S3, Amazon DynamoDB, and Amazon RDS, enabling efficient data integration and synchronization with existing AWS infrastructure.

  3. Pricing Model: Algolia offers a transparent pricing model based on the number of operations, records, and search traffic, making it suitable for applications with unpredictable usage patterns. It provides clear pricing tiers and offers a free trial for testing the service. Amazon CloudSearch, on the other hand, follows a pay-as-you-go pricing model based on instance and document batch size, along with additional charges for data transfer and search queries. It provides flexibility for scaling resources based on demand.

  4. Infrastructure and Scalability: Algolia operates a globally distributed infrastructure with multiple data centers, ensuring low latency and high availability for search requests. It automatically handles scaling, replication, and failover to provide a reliable service. Amazon CloudSearch leverages the scalable and fault-tolerant infrastructure of AWS, allowing automatic scaling of resources based on workload demands. It supports multiple availability zones and provides robust data redundancy and recovery mechanisms.

  5. Analytics and Monitoring: Algolia offers a comprehensive analytics dashboard that provides insights into search performance, user behavior, and conversion rates. It allows tracking and analyzing custom events, clickthrough rates, and conversion metrics for fine-tuning search relevance and effectiveness. Amazon CloudSearch integrates with AWS CloudWatch, enabling monitoring of search domain metrics, system health, and resource utilization. It provides configurable alarms and notifications for proactive monitoring and troubleshooting.

  6. Customization and Extensibility: Algolia provides extensive customization options through a powerful set of APIs, allowing developers to fine-tune search relevance, create custom ranking rules, and implement personalized user experiences. It offers flexible query rules, synonyms management, and rich filtering capabilities. Amazon CloudSearch supports advanced search features like faceting and sorting, along with customizable relevance tuning. It provides integration with AWS Lambda, enabling extensibility through serverless functions for customizing search behavior.

In summary, Algolia and Amazon CloudSearch differ in aspects such as real-time search experience, data integration options, pricing model, infrastructure scalability, analytics capabilities, and customization/extensibility features.

Advice on Algolia and Amazon CloudSearch
Akhil Kumar Singh
software developer at arzooo · | 7 upvotes · 16.1K views


All these details are stored in different tables like ORDERS, PAYMENTS, RETAILERS, STORES, CUSTOMERS, and INVOICES with relations. Right now we have only 10MBs of data with 20K records. So I need a scalable solution that can handle the search from all the tables mentioned and how can I make a dataset with so many tables with relations for search.

See more
Replies (1)
Christopher Wray
Web Developer at Soltech LLC · | 2 upvotes · 13.6K views

What e-commerce platform or framework are you using?

A lot of this depends on what your infrastructure already supports. Either of the options are a great choice so it comes down to what will be easiest to integrate and which search service is most affordable.

Elastic search is open source but you will need to configure and maintain it on your server. It may be more difficult to set up depending on the platform your app is built on.

Algolia has great documentation and is normally pretty easy to integrate but it can be pretty expensive.

I've never used Typsense but it seems like it would be a great option as well.

See more
Rana Usman Shahid
Chief Technology Officer at TechAvanza · | 6 upvotes · 380.8K views
Needs advice

Hey everybody! (1) I am developing an android application. I have data of around 3 million record (less than a TB). I want to save that data in the cloud. Which company provides the best cloud database services that would suit my scenario? It should be secured, long term useable, and provide better services. I decided to use Firebase Realtime database. Should I stick with Firebase or are there any other companies that provide a better service?

(2) I have the functionality of searching data in my app. Same data (less than a TB). Which search solution should I use in this case? I found Elasticsearch and Algolia search. It should be secure and fast. If any other company provides better services than these, please feel free to suggest them.

Thank you!

See more
Replies (2)
Josh Dzielak
Co-Founder & CTO at Orbit · | 8 upvotes · 284.4K views

Hi Rana, good question! From my Firebase experience, 3 million records is not too big at all, as long as the cost is within reason for you. With Firebase you will be able to access the data from anywhere, including an android app, and implement fine-grained security with JSON rules. The real-time-ness works perfectly. As a fully managed database, Firebase really takes care of everything. The only thing to watch out for is if you need complex query patterns - Firestore (also in the Firebase family) can be a better fit there.

To answer question 2: the right answer will depend on what's most important to you. Algolia is like Firebase is that it is fully-managed, very easy to set up, and has great SDKs for Android. Algolia is really a full-stack search solution in this case, and it is easy to connect with your Firebase data. Bear in mind that Algolia does cost money, so you'll want to make sure the cost is okay for you, but you will save a lot of engineering time and never have to worry about scale. The search-as-you-type performance with Algolia is flawless, as that is a primary aspect of its design. Elasticsearch can store tons of data and has all the flexibility, is hosted for cheap by many cloud services, and has many users. If you haven't done a lot with search before, the learning curve is higher than Algolia for getting the results ranked properly, and there is another learning curve if you want to do the DevOps part yourself. Both are very good platforms for search, Algolia shines when buliding your app is the most important and you don't want to spend many engineering hours, Elasticsearch shines when you have a lot of data and don't mind learning how to run and optimize it.

See more
Mike Endale
Cloud FirestoreCloud Firestore

Rana - we use Cloud Firestore at our startup. It handles many million records without any issues. It provides you the same set of features that the Firebase Realtime Database provides on top of the indexing and security trims. The only thing to watch out for is to make sure your Cloud Functions have proper exception handling and there are no infinite loop in the code. This will be too costly if not caught quickly.

For search; Algolia is a great option, but cost is a real consideration. Indexing large number of records can be cost prohibitive for most projects. Elasticsearch is a solid alternative, but requires a little additional work to configure and maintain if you want to self-host.

Hope this helps.

See more
Decisions about Algolia and Amazon CloudSearch

We originally had used Algolia for our search features. It's a great service, however the cost was getting to be unmanageable for us. Algolia's pricing model is based around the number of search requests and the number of records. So if you produce a large number of small records the price can quickly get out of hand even if your actual dataset doesn't take up that much space on disk. Spikes in internet traffic can also lead to unexpected increases in billing (even if the traffic comes from bots)

After migrating to Typesense Cloud we have been able to save A LOT of money without losing out on any of the performance we got from Algolia. I do not exaggerate when I say that our overhead for search is less than 25% of what it used to be. Typesense also has the following advantages:

  1. Their cloud offering lets you configure your Typesense nodes and specify how many you want to spin up. This allows you to manage costs in a manner that is way more predictable. (You basically pay for servers/nodes instead of records and requests)

  2. It's completely open source. We can spin up a cluster on our own servers or run it locally.

See more
Phillip Manwaring
Developer at Coach Align · | 5 upvotes · 37.2K views

The new pricing model Algolia introduced really sealed the deal for us on this one - much closer to pay-as-you-go. And didn't want to spend time learning more about hosting/optimizing Elasticsearch when that isn't our core business problem - would much rather pay others to solve that problem for us.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More