I highly recommend this software if its capabilities fall into what you need. It is very fast both in terms of indexing speed and search. It’s relatively simple to setup and start working against, and I have found it very reliable.<p>It works best when you have a SQL data store you want to index against, but with the real time index you can treat it more like elastic and other searches. However for that first use case of SQL, I don’t know of anything else that comes close to being as easy to use.<p>Simply point it at your database, give it a query to pull what you want to index and you are done. I suspect that this covers about 90% of use cases out there.<p>If you need more than what the DB native indexing is giving you give it a try.
See also this lightweight alternative to ES: <a href="https://github.com/zinclabs/zinc">https://github.com/zinclabs/zinc</a>
"We are excited to announce the addition of telemetry in this release. [...] This feature can be easily turned off in the settings if desired."<p>How did they know in the previous 5 major versions which part of the product to improve?
I looked for an up to date elasticsearch compatibility chart but was unable to find one.<p>I found an article from 2022 that did a compare/contrast but I wanted a feature by feature breakdown.
I've been running Manticore (previously SphinxSearch) on a faceted search heavy site with a million MAUs for 15 years. I'd definitely use it again for another project.<p>If the data that you want to search is entirely contained in a SQL database, it's an uncomplicated and powerful solution, definitely check it out. If not, Manticore may still be a nice solution for you, but I can't speak to that.
how does it compare to another c++ elasticsearch alternative that was on HN a few days ago: <a href="https://github.com/typesense/typesense">https://github.com/typesense/typesense</a>
Related: Meilisearch v1.0.0 release two days ago: <a href="https://news.ycombinator.com/item?id=34707727" rel="nofollow">https://news.ycombinator.com/item?id=34707727</a><p>I have been following these two libraries (Manticore and Meilisearch) very closely. Their simplicity, portability and performance gains over Elasticsearch are impressive.<p>Since two days ago, I am creating Python bindings for the core search engine of each of these two libraries, starting with <a href="https://github.com/AlexAltea/milli-py">https://github.com/AlexAltea/milli-py</a>.
Getting extreme performance, but as an embedded/self-contained package (basically same goals as SQLite).
What is people looking for in alternatives for elastic search? I have been toying in docker with a version of elastic search, fscrawler and workplace search to get a company to have better access to their knowdledge base. They have exchange, manuals, emails,images& video github and other stuff… does this alternatives have connectors too? Any experience on this?
Anytime I see an alternative to Elastic search on HN my first thought is how much of a shame it is to use something other than Lucene for text search because of just how powerful it really is.<p>Elasticsearch is a pain to tune and partition, and the JVM brings a whole set of operational issues but what's the point of better read/write performance when the actual search performance is worse?<p>I guess this makes sense for use cases where you care more about speed than the quality of results.
> You can now execute Elasticsearch-compatible insert and replace JSON queries, which enables the use of Manticore with tools such as Logstash and Filebeat<p>Looking at the docs I could only see _create and _doc but not _bulk endpoint support. How will that work with Logstash and Filebeat?