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
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- learning-notes/books/designing-data-intensive-applications.md at master · keyvanakbary/learning-notes · GitHubgithub.com
- Databases in 2025: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Databases in 2024: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Databricks: Leading Data and AI Solutions for Enterprisesmooncake.dev
- The Beginner's Guide to Databasestechnically.substack.com
- Database Fundamentalstontinton.com
- Introducing Husky, Datadog’s third-generation event store | Datadogdatadoghq.com
- Rebuilding Linear’s delta sync read pathlinear.app
- Two Sizes Fit Most: PostgreSQL and ClickHouse - The New Stackthenewstack.io
- Lance Format and LanceDB: Columnar Storage for the Embedding Age | Andrea Bozzo | Blogandreabozzo.github.io