OK, didn't notice that functionality when I've spent time with those, and to me they feel like more serious commitments, you know? There's more work involved and more maintenance and so on.
Especially ElasticSearch is rather fiddly and demanding, and I've seen exactly one production ES-system that impressed me, the rest were log-stores that could have used just about any database engine.
With Manticore I just apt it in and start pouring data into it immediately. Similar to how MySQL/MariaDB is almost frictionless when you run it locally with a root account, and neither ever starts to be annoying in resource consumption unless I actively mess up. I typically chose either (or DuckDB) when I have an idea or some ETL task I'd like to implement, over Postgres and ElasticSearch.
Especially ElasticSearch is rather fiddly and demanding, and I've seen exactly one production ES-system that impressed me, the rest were log-stores that could have used just about any database engine.
With Manticore I just apt it in and start pouring data into it immediately. Similar to how MySQL/MariaDB is almost frictionless when you run it locally with a root account, and neither ever starts to be annoying in resource consumption unless I actively mess up. I typically chose either (or DuckDB) when I have an idea or some ETL task I'd like to implement, over Postgres and ElasticSearch.