Need advice about which tool to choose?Ask the StackShare community!
Elasticsearch vs Typesense: What are the differences?
Elasticsearch and Typesense are both highly popular solutions for search and data retrieval. Let's explore the key differences between them.
Scalability: Elasticsearch is designed to be highly scalable, allowing for horizontal scaling by adding more nodes to a cluster. It can handle large amounts of data and scale to thousands of servers if needed. On the other hand, Typesense is built to be lightweight and optimized for low resource consumption. It is ideal for smaller deployments or when resource efficiency is a priority.
Querying: Elasticsearch offers a powerful and flexible query DSL (Domain Specific Language), which allows for complex queries and aggregations. It also supports full-text search, filtering, and sorting efficiently. Typesense, on the other hand, provides a simplified query syntax, making it easier to use and understand. It is optimized for simple search use cases and may not provide the same level of flexibility as Elasticsearch.
Schema-less vs Schema-based: Elasticsearch is schema-less, meaning that it can handle varying structures of documents within the same index. This flexibility can be beneficial when dealing with unstructured data. In contrast, Typesense follows a schema-based approach, where documents must adhere to a pre-defined schema. This ensures data consistency and more efficient indexing, but can be limiting when dealing with dynamic or evolving data structures.
Indexing Speed: Elasticsearch is optimized for fast indexing of data. It can handle high write loads and can index data in near real-time. This makes it suitable for use cases that require frequent updates to the index. Typesense, while it also has good indexing performance, may not be as fast as Elasticsearch in high-write scenarios.
Built-in Features: Elasticsearch comes with various built-in features like geolocation searches, language analyzers, and support for parent-child relationships. It also has a strong ecosystem of plugins and integrations. Typesense, on the other hand, focuses on providing a lightweight and easy-to-use search engine, with fewer built-in features. It may require additional customization or integration with external libraries for certain functionalities.
Community and Adoption: Elasticsearch has been around for a longer time and has a larger community and user base. It has been widely adopted by enterprises and has a more mature ecosystem. Typesense, being a newer player in the market, may have a smaller community and fewer resources available.
In summary, Elasticsearch offers scalability, powerful querying capabilities, schema-less structure, fast indexing, a wider range of built-in features, and a larger community. Typesense, on the other hand, focuses on being lightweight, resource-efficient, easy to use, schema-based, and tailored for simple search use cases.
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!
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.
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.
Pros of Elasticsearch
- Powerful api328
- Great search engine315
- Open source231
- Restful214
- Near real-time search200
- Free98
- Search everything85
- Easy to get started54
- Analytics45
- Distributed26
- Fast search6
- More than a search engine5
- Great docs4
- Awesome, great tool4
- Highly Available3
- Easy to scale3
- Potato2
- Document Store2
- Great customer support2
- Intuitive API2
- Nosql DB2
- Great piece of software2
- Reliable2
- Fast2
- Easy setup2
- Open1
- Easy to get hot data1
- Github1
- Elaticsearch1
- Actively developing1
- Responsive maintainers on GitHub1
- Ecosystem1
- Not stable1
- Scalability1
- Community0
Pros of Typesense
- Free5
- Facet search4
- Easy to deploy4
- Out-of-the-box dev experience3
- Ultra fast3
- Search as you type3
- Typo handling3
- Open source3
- Near real-time search2
- Super easy to implement2
- InstantSearch integration2
- Modern search engine2
- Restful1
- Great documentation1
- SaaS option1
Sign up to add or upvote prosMake informed product decisions
Cons of Elasticsearch
- Resource hungry7
- Diffecult to get started6
- Expensive5
- Hard to keep stable at large scale4