A Customer’s Journey: Migrating from NoSQL to a Cloud Native Distributed SQL Database
summary
A telecom stack migrates Cassandra to YugabyteDB to stop tombstone-driven slowdowns and gain distributed ACID transactions with low-latency multi-region reads, replacing compaction tuning and server-sprawl with automatic sharding and linear scaling. Migration uses discovery workshops, a single POC, bulk exporters plus temporary ETL, and deployment automation with Ansible playbooks and Kubernetes; cluster runs Raft, masters/tablet servers, and supports blue/green parallel runs. Outcome: production apps move with restored secondary-indexed point reads and predictable ops costs.
AI-written summary · about
chapters (12)
- 0:00Customer migration case
- 1:06Speaker background
- 4:59Telecom use case background
- 8:22NoSQL challenges
- 13:40New database requirements
- 16:30Evaluating migration options
- 17:56Why YugabyteDB
- 21:22Migration strategy
- 25:36Migration process
- 30:57NoSQL to distributed SQL
- 33:45Migration aspects
- 34:06Q&A
related talks
30mBuilding Cloud Native Applications on Distributed SQL Platform
19mEvolve: A Database Journey from Ground to Cloud
27mSparking our way to YugabyteDB: Our journey from ScyllaDB to
36m5 Hard-Learned Lessons from Successful Database Migration and Modernization
17mBuilding a Scalable and Performant SaaS Platform with YugabyteDB
30mFrom monolith to petabyte scale: Built a cloud-native, AI-ready data layer
28mDisrupting the Status Quo with Distributed SQL to Deliver Data-Driven Solutions
51mEmbrace, Extend, Evolve - Making PostgreSQL Work for a Cloud Native World