Introduction to YugabyteDB – Design and Architecture
summary
YugabyteDB claims ACID transactions with cloud native horizontal scaling by adding nodes, showing a concrete replication factor three example across four nodes and automatic re-replication after failures. It uses Raft consensus per tablet, a two‑phase commit for distributed transactions, and a DocDB storage layer built on RocksDB optimized for SSDs. Two APIs exist: YSQL (Postgres-compatible) with snapshot and serializable isolation, and YCQL for Cassandra‑style workloads.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:21What is Distributed SQL?
- 2:35Monolithic Databases vs Distributed Databases
- 4:27How do Distributed Databases Scale Out
- 5:12How do Distributed Databases Tolerate Failures
- 6:40Network Partition
- 8:00CAP Theorem
- 10:39ACID Compliance
- 12:33Components
- 14:19Component Services
- 17:21Sharding Layer
- 18:46Replication Layer
- 20:21Storage Layer
- 22:01Secondary Indexes
- 22:58Query Layer
related talks
27mIntroduction to YugabyteDB: Design and Architecture
25mYugabyteDB Technical Overview
30mBuilding Cloud Native Applications on Distributed SQL Platform
30mTechnical Comparison of YugabyteDB with Oracle and PostgreSQL
47mAnatomy of a Distributed SQL Database - YugabyteDB
01h 27mYugabyteDB YSQL Development
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
26mIntroducing YugabyteDB for PostgreSQL Users
