15 years of Database evolution in 20 minutes
summary
Couchbase starts as a merge of CouchDB and Membase and evolves into a multimodel platform with a focus on latency: distributed JSON key/value store, active-active replication implemented since ~2011, DCP change stream that syncs services, and a Kubernetes operator plus managed Capella. Key milestones: memcached users (Facebook/Twitter/YouTube) → automatic sharding, SQL for JSON (2014), recursive CTEs (2023), vector store 2023–24, Couchbase Mobile (SQLite JSON offline), and a columnar analytics service (Capella columnar) now in cloud.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 0:49Relational databases before cloud
- 2:54Rise of caching and NoSQL
- 5:25CouchDB and JSON revolution
- 7:09Merge into Couchbase
- 8:33NoSQL trends and challenges
- 10:38SQL for JSON and evolution
- 13:05Multimodel database platform
- 15:50Couchbase Mobile and offline sync
- 17:18Couchbase Capella cloud offering
- 18:22Analytics and AI integration
- 22:52Q&A and closing
related talks
26mHow to select a future-proof database
59mData Modeling for
01h 02mNext Generation Data Storage with CouchDB
21mUse cases that drive the need for NoSQL databases
45mSpring Data Couchbase: A Coming of Age
46mApache CouchDB Internals, Now and Then
11mEvolution of Development Priorities in Key-value Stores Serving Large-scale Applications
15mWhen is it time to modernize your AWS database platform?