Building Cloud Native Applications on Distributed SQL Platform
summary
Argues that YugabyteDB lets teams keep familiar SQL while gaining NoSQL scale, showing a running architecture: Postgres + CQL API over a key/value storage with Raft consensus with single leader per shard, plus automatic hash/range/geo sharding. Demonstrates online scale up/down, multi-region active‑active replication for low latency, no downtime for patches or failover, and a YB Anywhere DBaaS option; claims these remove common CQRS/read‑replica workarounds and simplify global backup and DR.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:51Distributed SQL importance
- 5:07Cloud-native DB challenges
- 9:24Scaling with distributed SQL
- 11:34Manual sharding issues
- 13:43NoSQL strengths/limits
- 16:30YugabyteDB hybrid
- 18:35CQRS patterns sync
- 20:21Read replicas consistency
- 21:24YugabyteDB consistency
- 22:25High availability failover
- 24:13YugabyteDB Anywhere
- 25:38Global multi-region scale
- 26:21Disaster recovery backup
- 27:22Cloud-native benefits
- 28:49YugabyteDB ideal choice
- 29:10Q&A
related talks
27mIntroduction to YugabyteDB – Design and Architecture
25mYugabyteDB Technical Overview
47mAnatomy of a Distributed SQL Database - YugabyteDB
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
08mScalable GraphQL Applications Powered by Cloud-ready Distributed SQL Database
27mIntroduction to YugabyteDB: Design and Architecture
30mTechnical Comparison of YugabyteDB with Oracle and PostgreSQL
25mDiscover the Easiest Path to Distributed DBaaS: Yugabyte Cloud