Most data teams run two systems: one database for transactions, another for analytics, with data copied between them. It works, but the pipelines are brittle, the copies drift, and governance gets complicated.
At this year's Data AI Summit, we announced LTAP, a new architecture that does away with the second copy entirely. With LTAP, transactions and analytics run on a single copy of your data, stored in open formats that both sides read directly. Analytics always sees the freshest data your application just wrote, with no CDC, no mirroring, and no slowdown to your transactional workload.
Databricks co-founder
@rxin walks through the architecture that makes this possible, starting at the storage layer of a traditional database and building from Lakebase up to LTAP.
databricks.com/blog/lakebase…