Apache Lucene
Hacker ApprovedThe most recommended of 4 full-text search libraries
Mature, heavily optimized search library that makes full-text search straightforward, with fuzzy, stemmed and faceted matching. Critics say it adds complexity and toil and question its fit for some projects.
Mature, heavily optimized search library that makes full-text search straightforward, with fuzzy, stemmed and faceted matching. Critics say it adds complexity and toil and question its fit for some projects.
15 people gave an opinion
- recommend it
- 12
- criticize it
- 3
- approval share
- 80%
Recommended in 6 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 12 people recommend itNeeds 10 or more, met.
- 4 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 6 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Mature, heavily optimized technology
“Lexical is much easier to control, iterate and debug. The tools are incredibly mature.”
Comment from 26 Aug 2026 in “RAG Is Simpler Than You Think” “Lucene is of course well known to be heavily optimized”
Comment from 17 Nov 2025 in “Building a Simple Search Engine That Works” “It's incredibly mature technology.”
Comment from 10 Mar 2026 on Hacker News Makes search straightforward to build
“if you use a library like Lucene, it does not need to be hard at all”
Comment from 17 Nov 2025 in “Building a Simple Search Engine That Works” “Before Lucene, search was really hard”
Comment from 20 Nov 2025 in “Building a Simple Search Engine That Works” “Lucene is often all you need.”
Comment from 3 Nov 2025 in “The Case Against PGVector” Solid word matching and tokenization
“Lucene and friends are fantastic about word matching, fuzzy searches, stem searches, phonetic searches, faceting and more”
Comment from 3 Nov 2025 in “The Case Against PGVector” “Lucene white space tokenization is pretty good for dumb exact or close enough”
Comment from 21 Nov 2025 in “Ask HN: How would you architect a RAG system for 10M+ documents today?” Separate index alongside SQL
“I've always preferred to use SQL as the system of record and then build/maintain an external Lucene index”
Comment from 19 Sep 2026 in “Tin: full-text search for Postgres” “It lives in a dir on disk. True, it's a separate database, but one optimized for this problem.”
Comment from 17 Nov 2025 in “Building a Simple Search Engine That Works”
What people warn about
Each mark is one comment
Adds toil, fragility and complexity
“Vendoring a library like this into an app seems like a lot more toil than just writing the native multiprocessing python code”
Comment from 25 Jul 2026 in “Show HN: Lucen a Python compiler that parallelizes for-loops via comment pragmas” “The fragility, security risk, and complexity added by basically writing a subdialect of Python”
Comment from 25 Jul 2026 in “Show HN: Lucen a Python compiler that parallelizes for-loops via comment pragmas”
Other full-text search libraries people recommend
The three most recommended other full-text search libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 4 full-text search libraries, rankedWhat people said
18 of the 19 comments that mention it, newest first. Each links to the original comment.
“I've always preferred to use SQL as the system of record and then build/maintain an external Lucene index”
“Lexical is much easier to control, iterate and debug. The tools are incredibly mature.”
“Approaching search by just tossing the data in Lucene is how you end up with Confluence's search box”
“it's not a project I personally am comfortable using at this time due to the combination of its purpose, maturity, and development methodology”
“you shouldn't have to touch the loop you already have”
“The fragility, security risk, and complexity added by basically writing a subdialect of Python”
“This should be part of the Standard Library if so efficient.”
“Vendoring a library like this into an app seems like a lot more toil than just writing the native multiprocessing python code”
“I've had great success letting an agent loose on an Apache Lucene instance”
“It's incredibly mature technology.”
“Lucene white space tokenization is pretty good for dumb exact or close enough”
“Before Lucene, search was really hard”
“if you use a library like Lucene, it does not need to be hard at all”
“Lucene is of course well known to be heavily optimized”
“It lives in a dir on disk. True, it's a separate database, but one optimized for this problem.”
“In Solr/Lucene it used to mean you were dead. I'm sure they fixed that”
“Lucene and friends are fantastic about word matching, fuzzy searches, stem searches, phonetic searches, faceting and more”
“Lucene is often all you need.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.