Algolia vs Elasticsearch

Algolia

Algolia is great anytime you need client search. I would never use it to do any automated tasks or anything like that, though. It's great for human use, and I don't know if anyone would ever want to use it for anything other than client-search, but Algolia knows its domain very well and solves client search more easily than any alternative I've seen.

Read full review

Eli Allen

Founder

CurtsyComputer Software, 11-50 employees

View all 5 answers on this topic

Elasticsearch

Elasticsearch is extremely well suited for structured (faceted) search, full-text search, and analytics workloads. Elasticsearch and the ELK stack are also a good fit for operations teams that want to be able to interrogate their logs in an online (read: fast) query tool. Elastic is amazing at creating super fast search experiences over very large datasets, where traditional RDBMS systems are either too costly or too slow.

Read full review

Anatoly Geyfman

Founder & CEO

CarevoyanceHealth, Wellness and Fitness, 1-10 employees

View all 25 answers on this topic

Pros

Algolia is lightning quick -- the fastest we found
Algolia has great tech support, tons of documentation, and many high quality ready-made plugins
Algolia allows for a high degree of customization

Read full review

Michael Riess

Owner

Riess GroupInformation Technology and Services, 11-50 employees

View all 5 answers on this topic

Super-fast search on millions of documents. We've got over 2 billion documents in our index and the retrieve speeds are still in the < 1-second range.
Analytics on top of your search. If you organize your data appropriately, Elasticsearch can serve as a distributed OLAP system
Elasticsearch is great for geographic data as well, including searching and filtering with geojson, and a variety of geospatial algorithms.

Read full review

Anatoly Geyfman

Founder & CEO

CarevoyanceHealth, Wellness and Fitness, 1-10 employees

View all 25 answers on this topic

Cons

Customising the react packages can be difficult. Easy to send an excessive amount of requests
Customising ranking is restricted to prioritising factors, rather than weighting each factor individually
Costs can escalate dramatically when you expand your traffic

Read full review

Rich Warren

Growth Engineering Lead

Fat LamaInternet, 11-50 employees

View all 5 answers on this topic

Their documentation needs a lot of imporvement
Difficult to understand query language
New updates are difficult to adopt

Read full review

Tarun Mangukiya

Co-Founder

IconscoutDesign, 1-10 employees

View all 25 answers on this topic

Likelihood to Renew

No score

No answers yet

No answers on this topic

Ask the community to sound off

Elasticsearch10.0

Based on 1 answer

We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.

Read full review

Aaron Gussman

Senior Technologist

HumanGeoDefense & Space, 51-200 employees

View all 1 answers on this topic

Usability

No score

No answers yet

No answers on this topic

Ask the community to sound off

Elasticsearch10.0

Based on 1 answer

To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching.If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.

Read full review

Verified User

Vice-President in Information Technology

Computer Software Company, 1-10 employees

View all 1 answers on this topic

Implementation

No score

No answers yet

No answers on this topic

Ask the community to sound off

Elasticsearch9.0

Based on 1 answer

Do not mix data and master roles. Dedicate at least 3 nodes just for Master

Read full review

Verified User

Contributor in Information Technology

Pharmaceuticals Company, 51-200 employees

View all 1 answers on this topic

Alternatives Considered

Algolia was by far and away the easiest of the three to implement. PostgreSQL has many search modules that can be used on top of your usual database, however, none are particularly efficient and can quickly become overwhelmed at scale. Equally, they do not handle business metric weightings well. Elastic search is what Algolia is built on and works well, however, it would require a lot more manual setup to ultimately get to a solution that is similar and likely worse than Algolia offer. Both Algolia and elastic search suffer from the problem of having to keep two items databases in sync.

Read full review

Rich Warren

Growth Engineering Lead

Fat LamaInternet, 11-50 employees

View all 5 answers on this topic

Power and simplicity along with performance.

Read full review

Josh Kramer

Senior Software Engineer

OctivComputer Software, 51-200 employees

View all 25 answers on this topic

Return on Investment

Decreased SEO landing page load speeds, due to faster search results.
Increased user conversion from search
Reduced server costs

Read full review

Rich Warren

Growth Engineering Lead

Fat LamaInternet, 11-50 employees

View all 5 answers on this topic

Positive impact. We could, for the first time, implement a really useful system to support our business users in working with our big data repositories.

Read full review

Trung Le

Technical Architect / IT Manager

Talentnet CorporationHuman Resources, 201-500 employees

View all 25 answers on this topic