OpenSearch-Dashboards VS manticoresearch

I hate OpenSearch with a passion, an absolutely horrid lagging project that can't get basic autocomplete working (https://github.com/opensearch-project/OpenSearch-Dashboards/...)

but still manages to suck the air out of the room when you want Elasticsearch because AWS already has the company's billing details and no one wants to figure out paying another provider.

Time to look at the data in OpenSearch with the help of OpenSearch Dashboards!

Create dashboards to show and graph whatever you want. - https://opensearch.org/docs/latest/dashboards/index/

Note, you need to do it in the root folder of a clone from https://github.com/manticoresoftware/manticoresearch

Interesting, how does it compare to Mantico search?

Where Manticore Search? https://manticoresearch.com/

It's not open source since 2017. The open source fork is https://github.com/manticoresoftware/manticoresearch

I haven't looked at the code, but I've seen https://github.com/manticoresoftware/manticoresearch popping up in a few places. Might be worth looking at. It would be great to have a faster drop-in replacement for Elasticsearch that's not written in Java. They blogged about it here: https://manticoresearch.com/blog/manticore-alternative-to-elasticsearch/

I don't see anywhere where they claim that it's faster simply because it's written in C++. They do mention that they make use of C++ to add low level optimizations that make queries faster and the memory imprint smaller, but any claims about performance in the readme are linked to benchmarks to back up their claims

https://github.com/manticoresoftware/manticoresearch/

https://db-benchmarks.com/test-taxi/#manticore-search-vs-ela...

contributors