HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
opensearch-project
OpenSearch
Java2022–2025
opensearch-project / OpenSearch

OpenSearch

🔎 Open source distributed and RESTful search engine.

Data & DatabasesSystems & InfrastructureSearch & Information Retrieval
Explore on GitHubRead Hacker News discussions
12Distinct people
13Mentions
0Explicit recommenders
14KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🔎 Open source distributed and RESTful search engine.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 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 year13 dated mentions

Observed mentions: 2022-02-16 23:37:32 UTC to 2025-11-03 15:04:39 UTC.

0123452022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC220
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404

What Hacker News says

13 sources
wokwokwok·Mar 29, 2024
The reality is that open search will be (if it is not already) more widely deployed and “battle tested” with bugs that production use raise resolved in it. The narrative that opensearch is some kind of unsafe abandonware is clearly nonsense when you read the commit log: https://github.com/opensearch-project/OpenSearch/commits/mai... All I can say is, sure, if you want elastic use elastic. …but opensearch is fine. I use it and have no problem with it.
In The race to replace Redis
hardwaresofton·Oct 24, 2022
Oh! Damn it I forgot about manticore -- I had seen it before but forgot to include it. Eventually all of these projects will be highlighted on Awesome F/OSS (https://awsmfoss.com), but for now I'm just going to dump my bookmarks here for other people, since I'm leaving awesome projects out: Search Engines AWS OpenSearch https://github.com/opensearch-project/OpenSearch https://github.com/opensearch-project/OpenSearch-Dashboards https://github.com/opensearch-project/perftop https://github.com/go-ego/riot https://groonga.org/ https://github.com/groonga/groonga https://github.com/meilisearch/MeiliSearch https://github.com/mosuka/bayard https://github.com/nezaboodka/nevod https://github.com/searx/searx https://github.com/stryku/okon https://github.com/toshi-search/Toshi https://github.com/typesense/typesense https://github.com/valeriansaliou/s
Read the rest
onic Algolia https://github.com/marconi1992/algolite https://quickwit.io/ https://github.com/quickwit-inc/quickwit https://docs.meilisearch.com/ https://github.com/prabhatsharma/zinc phalanx https://github.com/blugelabs/bluge https://github.com/mosuka/phalanx https://github.com/mosuka/blast ManticoreSearch https://github.com/manticoresoftware/manticoresearch https://github.com/manticoresoftware/docker https://manticoresearch.com/blog/manticore-alternative-to-el... https://manticoresearch.com/ https://manual.manticoresearch.com/Introduction https://forum.manticoresearch.com/t/manticore-search-cheatsh... https://forum.manticoresearch.com/ Whoosh https://whoosh.readthedocs.io/en/latest/ https://pypi.org/project/Whoosh/ lyra https://github.com/nearform/lyra https://nearform.github.io/lyra/ https://github.com/LyraSearch/lyra https://lyrasearch.io/ flexsearch https://github.com/nextapps-de/flexsearch#performance-benchm... https://pagefind.app/docs/ Lucene https://github.com/apache/lucene https://lucene.apache.org/ ZincSearch https://zincsearch.com/ Solr https://solr.apache.org/ https://solr.apache.org/operator/ https://solr.apache.org/guide/solr/latest/getting-started/so... https://github.com/apache/solr https://solr.apache.org/guide/solr/latest/deployment-guide/s... Konnu https://gitlab.com/shadowislord/konnu Quickwit QuickWit + Clickhouse https://clickhouse.com/docs/en/guides/developer/full-text-se... https://clickhouse.com/docs/en/sql-reference/functions/strin... There is no way I can get to running all of these (this project was supposed to be quick!!), but I will run the ones I noted earlier, and probably manticore too since it was high on my list since it's quite polished looking.
In Sonic: Fast, lightweight and schema-less search backend
hardwaresofton·Oct 24, 2022
Wow it's weird that this comes up, I'm actually running a site I am going to repost to HN today that I want to use as a testbed for search engines (kind of like an extension to my recent collaboration with supabase[0]). Right now I've got the site going on just Postgres FTS + trigram and it's pretty darn fast, looks like I need to test sonic too. Going to burn some midnight oil (in my timezone, anyway) and get it out -- though sonic isn't implemented yet! Anyway to make this comment useful to people, here's my short list of engines that I want to run in parallel: - MeiliSearch (https://github.com/meilisearch/MeiliSearch) - TypeSense (https://github.com/typesense/typesense) - Lyra (https://github.com/LyraSearch/lyra) - OpenSearch (https://github.com/opensearch-project/OpenSearch) - ZincSearch (https://github.com/prabhatsharma/zinc) - Sonic
Read the rest
(https://github.com/valeriansaliou/sonic) There isn't enough out there comparing all these for the simple typical fuzzy search/search box usecase, so I'm adapting a little podcast search site I made to try and use all of these at the same time. So far only Postgres though, will try and add Meilisearch today and post it! Like other people are pointing out, most of these engines won't have all the features of ES (or more accurately Lucene) but I am pretty convinced that most of the time it doesn't actually matter and if someone is searching on your site excessively maybe there's a problem with your UX (unless you're a search engine or repository of information). [0]: https://supabase.com/blog/postgres-full-text-search-vs-the-r...
In Sonic: Fast, lightweight and schema-less search backend
francoismassot·Sep 22, 2022
(disclaimer: I'm one of the cofounder of Quickwit.io, we are doing log search) (edited to add vector search category and add manticore) When looking at OSS search projects, it's nice to have a rough ideas of the different use cases, here is the list I have in mind: - user facing search (think algolia): elasticsearch[1]/opensearch[2], meilisearch[3], typesense[4] - enterprise search: elasticsearch/opensearch - log search: elasticsearch/opensearch, loki[5], quickwit[6], zincsearch[7] - vector search: Milvus[8], Qdrant[9], Vald[10] Weaviate[11] Vespa.ai[12] is great but I don't really know in which category to put them, user facing and enterprise search seems to work well with them. It's interesting to note that Elasticsearch and Opensearch are general purpose search engine, Solr as well. They are all powered by Lucene, the popular and per
Read the rest
formant search engine library. Another general purpose search engine is Manticore search[13]. I would love to see some benchmarks by category :) Note: I don't know well ZincSearch and put it in the log search as said on their front page. [1]: https://github.com/elastic/elasticsearch [2]: https://github.com/opensearch-project/OpenSearch [3]: https://github.com/meilisearch/meilisearch/ [4]: https://github.com/typesense/typesense [5]: https://github.com/grafana/loki [6]: https://github.com/quickwit-oss/quickwit [7]: https://github.com/zinclabs/zinc [8]: https://github.com/milvus-io/milvus [9]: https://github.com/qdrant/qdrant [10]: https://github.com/vdaas/vald [11]: https://github.com/semi-technologies/weaviate [12]: https://github.com/vespa-engine/vespa [13]: https://github.com/manticoresoftware/manticoresearch
In ZincSearch – lightweight alternative to Elasticsearch written in Go
SemanticStrengh·May 27, 2022
I hate the fact that OpenSearch divide in a bipartite the human resources allocated at improving elasticsearch, which is a tragedy. The hypocrisy is strong at amazon, they have allocated a lot of engineers on OpenSearch and yet their number of contributions pre-fork drama was much much lower (although they were still an important contributor though). But once the management has control and developers can have their own NIH dopamine release, humans are eager to work.. For this human resources reasons, I hope the OpenSearch distraction dies in darkness. However, beside my utilitaristic goals, I am also one of the only person caring about the technology. And it happens that the technology is generally not found in ElasticSearch but in the much more salient project: Lucene, which it uses. However, despite its big humans resources, ElasticSear
Read the rest
ch does a great job at NOT exposing Lucene features and optimizations... Lucene especially has developped 2 major optimizations the last decade unexposed in ES, one being about shards (don't recall the name), the other being concurrent search. And it happens that the NIH syndrome at amazon allow them to at least reconsider those frozen choices in ES. https://github.com/opensearch-project/OpenSearch/pull/1500 And I am eager to see the performance implications it will have although the ES approach has some pros too. In this issue, I descibe what ElasticSearch would do for parallelism, in an ideal world: https://github.com/elastic/elasticsearch/issues/80693
In OpenSearch 2.0

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.