1. Home
  2. Enterprise Search Software
  3. Apache Lucene Reviews
  4. User Review of Apache Lucene
Efficient Open Source Search Engine
January 21, 2021

Efficient Open Source Search Engine

Sirish Vadala | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Apache Lucene

Apache Lucene is being used across multiple applications where data keeps updating continuously. Being open source and the efficiency with which the search engine operates, its the perfect solution to implement dynamic text search. The accuracy of the search results is impressive and wouldn't make business sense to implement external products like Google search for a small scale data set.
  • Fast indexing, with proper optimization I can index a Gig of data in 2 mins.
  • Easy integration with web crawlers
  • Quick and Accurate Results
  • Flexible sorting option for results based on the search field and relevance
  • Scalable issues especially when the index grows in size with millions of documents.
  • The Boolean scoring model could be better.
  • Difficulty setting up on cluster based environment.
  • Cost effective
  • Opensource and easily customizable
  • Active community and feedback forums
The search and index performance of [Apache] Lucene is excellent and the quality of results is good, if not better. For implementing it with small scale applications it is a no brainer, Lucene is the best and most cost effective solution. Learning curve is not too steep either.

Do you think Apache Lucene delivers good value for the price?

Yes

Are you happy with Apache Lucene's feature set?

Yes

Did Apache Lucene live up to sales and marketing promises?

Yes

Did implementation of Apache Lucene go as expected?

Yes

Would you buy Apache Lucene again?

Yes

Apache Lucene is a perfect text search implementation where the heap space usage needs to be kept to its minimal. It also enables search based on various search fields and most importantly the search and index process can happen simultaneously. The only scenario where it might be less appropriate would be when the index size grows too big. We have witnessed few scalable issues where the search would take a while when the index size is too large.