State in a stateless world: data serving in the cloud
summary
Argues that state still matters in cloud-native stacks and gives concrete choices: use distributed SQL (CockroachDB, YugabyteDB, Aurora DSQL) to get transactions with horizontal scale, use read replicas or sharding for throughput, and build dashboards on OpenSearch for dashboards when queries are eventually consistent. Recommends the 3-2-1 backup rule, cross-AZ/region replication and offline WORM copies to survive ransomware, and warns that a monolithic single-writer DB already deployed causes visible operational pain.
AI-written summary · about
chapters (8)
- 0:00Introduction and Overview
- 1:00Challenges with Traditional Databases
- 2:17Types of Databases
- 6:26Scaling and Reliability
- 13:03Backup Strategies
- 16:05Choosing the Right Database
- 17:39Example Use Case
- 20:13Key Takeaways and Conclusion
related talks
51mDatabase systems: a decade of disruption and innovation
26mNewSQL: concepts, realities and when you should embrace it
29mModern Database Architecture: From SQL to NoSQL & Distributed SQL
44mRunning Non-Cloud-Native Databases in Cloud-Native Environments
10m⚡ Lightning Talk: Navigating the Complexities of Stateful Workloads in Kubernetes
30mBuilding Cloud Native Applications on Distributed SQL Platform
24mDoing Data as a Frontend Developer
38mNot all data is created equal: NoSQL