HTAP is Dead
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
A veteran database engineer who spent 10 years building HTAP systems at SingleStore argues that HTAP as a unified database architecture never achieved product-market fit. The post traces the history from single-database systems in the 1980s through the OLTP/OLAP split, the NoSQL era, the NewSQL and cloud data warehouse movements, and the 2014 coining of HTAP by Gartner. Key reasons HTAP failed include the difficulty of replacing entrenched OLTP systems, most workloads not needing distributed OLTP, cloud-native architectures favoring shared-disk over shared-nothing, and organizational silos between product engineering and data teams. Today, the modern data stack — CDC pipelines, open table formats like Iceberg, query engines like Spark and Trino, and real-time layers like ClickHouse — effectively implements HTAP through composition rather than consolidation, with the core challenge now being making the lakehouse real-time ready.
