What users are saying about
9 Ratings
93 Ratings
9 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.5 out of 101
93 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.9 out of 101

Add comparison

Likelihood to Recommend

Apache Lucene

Apache Lucene offers great full-text search library that makes it easy to add search functionality to a website or other applications. Lucene is ideal if you want low-level access to the indexes and its APIs. For general purposes, Apache Solr, the web application built atop of Lucene can be used instead. Apache Solr comes with caching, HTTP/ JSON APIs and a simple web administration console.
No photo available

Elasticsearch

Elasticsearch is the gold standard for text-based search. Across large data sets it performs admirably, and we will certainly make it our first choice search solution in the future. For a use case where needs are simple and regular database queries might suffice, Elasticsearch may or may not provide any benefits.
No photo available

Pros

  • We found Apache Lucene to be extremely performant in querying large amounts of data and retrieving the correct files based on the metadata provided.
  • The online community offers great support for the product. Even though it is an open source tool, it is not difficult to find help online for it.
  • When we were creating a proof of concept application, we found that the software worked just as well, while being run locally on a resource-limited PC.
No photo available
  • Lightning fast
  • Easily scalable
  • Powerful feature set
No photo available

Cons

  • We had difficulty porting the project to a cluster based environment on the cloud.
  • For our particular use case of retrieving documents based on text pattern matching, the program worked efficiently however, we did not find many resources for image pattern recognition based on their metadata.
No photo available
  • Additional complexities when in need of frequent & rapid updates to the Elasticsearch data set
  • New syntax can be confusing, particularly with advanced features and more powerful queries
No photo available

Likelihood to Renew

No score
No answers yet
No answers on this topic
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.
Aaron Gussman profile photo

Usability

No score
No answers yet
No answers on this topic
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.
No photo available

Implementation

No score
No answers yet
No answers on this topic
Elasticsearch9.0
Based on 1 answer
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
No photo available

Alternatives Considered

No photo available
When we first evaluated Elasticsearch, we compared it with alternatives like traditional RDBMS products (Postgres, MySQL) as well as other noSQL solutions like Cassandra & MongoDB. For our use case, Elasticsearch delivered on two fronts. First, we got a world-class search engine out of it, that we custom-built for our specific domain (healthcare). We've got, easily, the most expressive (easy to use & powerful) healthcare search engine out there. Second, along with the search, we also received an analytics engine that could do most analytics jobs as quickly as it retrieved search results. Overall, it would be very difficult for us to find a single solution for these two different problems.
Anatoly Geyfman profile photo

Return on Investment

  • Being an open source project we did not have to pay any licensing fees for using Apache Lucene. It has greatly improved our search functionality in our web apps.
No photo available
  • We have had great luck with implementing Elasticsearch for our search and analytics use cases.
  • While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
  • We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
Anatoly Geyfman profile photo

Pricing Details

Apache Lucene

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

Elasticsearch

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details