The relational model in the modern development age
summary
Covers how relational schema management creates operational friction for developers and presents a modern paradigm that restores developer ownership, using features added to Vitess (the CNCF sharding/proxy system) as the example. Explains problems like complex schema deployments, lack of conflict resolution, and irreversibility, and describes Vitess capabilities for hiding operational complexity, scheduled schema migrations, revertible (undeploy) changes, and aligning schema with code via declarative schemas, idempotent deployments, and version control.
AI-written summary · about
related talks
38mVitess: Schema Changes at Scale
11mRationale for Relational
22mLessons DevOps Can Teach Us About Managing Internet Scale Schemas
51mVitess beyond YouTube
28mThe Cloud is Inevitable
40mVitess: Introduction And New Features
43mVitess and a Kubernetes Operator
34mInside Vitess: Building Resilient, Distributed Databases