SAsAbakumoff·Oct 24, 2017
I mean, we have bleve[0]. What else do you need, really?
[0] https://github.com/blevesearch/bleve
In Riot – Full-text search engine in Goblevesearch
bleve
Go2014–2025
blevesearch / bleve
bleve
A modern text/numeric/geo-spatial/vector indexing library for go
19Distinct people
27Mentions
0Explicit recommenders
11.3KGitHub stars
What to know before exploring
What it is
A modern text/numeric/geo-spatial/vector indexing library for go
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- quickwit-oss/tantivy · linked in 8 of the same discussions
- meilisearch/meilisearch · linked in 4 of the same discussions
- toshi-search/toshi · linked in 4 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year27 dated mentions
Observed mentions: 2014-09-06 18:35:24 UTC to 2025-10-09 19:41:29 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesAlso, for consideration: Bleve (https://github.com/blevesearch/bleve)
I'm in the process of building my own search engine (as a learning exercise, but also because it's related to my day job). I've learned that it's one thing to write a full-text search engine, like this one, and it's quite another to do field-specific searches with faceting support and so on, like Algolia and Lucene-based search engines do.
That said, this is clean and simple. I like it. I can definitely learn from this.
In Riot – Full-text search engine in GoAlso, the code of a test could be used as the documentation. Just recently I started using bleve(https://github.com/blevesearch/bleve). Documentation is quite poor, but I was able to learn the product entirely from the code of its unit tests. That's not normal though.
In The tragedy of 100% code coverage (2016)Have you seen Bleve?
https://github.com/blevesearch/bleve
I have only tried it for an hour or two, and can't speak for its search result quality, but it seems promising.
On my laptop, with an index of 10,000 documents each containing 200 random words, it takes about 110ms to perform a fuzzy search. Half of that is the actual search, the other half is the process/initialization overhead.
In How Discord Indexes Billions of Messages Using Elasticsearch