Evolutionary Database Design & Architecture
summary
Argues that databases can evolve using concrete patterns: apply a Strangler pattern and an expand–transition–contract sequence to add columns, move data, then drop old schema; use views or generated columns as facades so legacy consumers keep working; migrate stored procedures into services to remove DB coupling. Tests encode database behavior, migration scripts live in CI and deploy with the app, and developers pair with DBAs. Gives examples: splitting name into first/last with triggers or data-migration, handling duplicate VINs before adding a unique constraint.
AI-written summary · about
chapters (14)
- 0:00Start
- 10:17Add Foreign Key Constraint
- 10:34Introduce Read Only Table
- 12:10Migrate method from database
- 16:19Simple Scenario
- 16:32Synchronize Data Scenario
- 17:46Migrate and Synchronize Data Scen
- 20:02Create façade in database
- 21:28Another example
- 22:45Refactoring Enablers
- 25:45Guide to successful refactoring
- 31:35Practices
- 31:54Test the Behavior of Database
- 36:07Automate Deployment
related talks
51mThe Evolution of Database Architectures
08mDatabase as Code. Not only migrations
30mExpand Contract Pattern for Continuous Delivery of Databases
45mEnabling Continuous Delivery with Database Practices
31mHelp! My Database Is The Bottleneck
31mDevOps Practices for the Database Team
01h 02mDesign Good Schemas - Get a Better Database
19mExpand Contract Pattern for Continuous Delivery of Databases