From OLTP & OLAP to HTAP and LTAP: The Evolution Toward a Lakehouse-Native Data Architecture
I am still second-reading Designing Data-Intensive Applications, and recently came across HTAP. It immediately made me think about hashtag #Databricks announcement of hashtag #LTAP and how it fits into the evolution from databases to the Lakehouse. The story starts with two very different workloads: - OLTP, Online Transaction Processing, runs operational applications. Handling workloads require low latency, high concurrency and reliable transactions (recording payments...). - OLAP, Online Analytical Processing, helps organizations understand what is happening across large volumes of data (reporting, ML...). Traditionally, these workloads were separated. Operational data lived in transactional databases and was later "copied" into analytical systems. 🔴 hashtag #HTAP , Hybrid Transactional/Analytical Processing, then emerged to bring these two worlds closer together. HTAP is not one specific implementation. The common objective is to support transactional and analytical pr...