Full-text search X times faster: Inverted index vs. SQL OLAP
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Inverted indexes, popularized by Elasticsearch and Lucene, were designed for consumer web search with rich tokenization and scoring. For observability and security log workloads, these features become antipatterns — developers need grep-style substring matches, not stemmed token lookups. SQL OLAP databases like ClickHouse can be 10x+ faster and more cost-efficient for this use case by using raw scans with skip indexes (e.g., bloom filters), columnar storage with tailored compression, and vectorized query execution. The post also discusses the migration challenge: organizations like Uber have 10k Kibana dashboards they can't easily move, while others like Zomato saved $1M/year by switching to ClickHouse. The author's product, Quesma, aims to bridge the Elastic ecosystem with SQL analytical backends.
Table of contents
How we got there: The rise of observability full-text searchHow Elasticsearch full-text search worksHow analytical full-text is differentHow to be 10 times faster in analytical searchSQL analytical data warehouse for observability and security dataBest tool for the job,Sort: