From monolith to Lakebase to LTAP: rethinking the database from storage up | Databricks Blog
databricks.com · 4,018 words · saved by 1 readers
When
From monolith to Lakebase to LTAP: rethinking the database from storage up | Databricks Blog Skip to main content Summary Almost every traditional database keeps its write-ahead log and data files on one machine's disk, which is the root cause of data loss risk, expensive read replicas and high-availability clones, and analytics queries that drag down transactions. Lakebase makes Postgres compute stateless by externalizing the log and data files into independent cloud services (SafeKeeper and PageServer), unlocking unlimited storage, elastic compute, durable writes, simpler HA, and instant bra
saved by
related reading
- Databricks: Leading Data and AI Solutions for Enterprisesmooncake.dev
- How to Rack 30 Petabytes of Storage | blogsi.inc
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- DuckLake: SQL as a Lakehouse Formatduckdb.org
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- The Beginner's Guide to Databasestechnically.substack.com
- How to design resilient and large scale data systemsblog.dataengineer.io
- What I Learned From The Modern Data Stack Conference 2021 - James Lejameskle.com
- Databases in 2025: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Two Sizes Fit Most: PostgreSQL and ClickHouse - The New Stackthenewstack.io
- The startup's Postgres survival guidehatchet.run