Winning at Continuous Deployment: The Art of Safe Contract Changes
summary
Shows a concrete failure mode when changing an API and a schema during rolling deploys: a demo web app on AWS (deployed with CDK) swaps a single "name" field for "firstName/lastName", runs an automated looped test (10 iterations) and reproduces errors from mixed 100 nodes V1/V2 pairs. Presents the practical solution expand-contract: 1) expand server to accept both versions, 2) switch clients, 3) remove old contract; demo code and GitHub commit history confirm zero-downtime success when applied.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:08Continuous Deployment vs Continuous Delivery
- 4:05Contract in Software
- 5:31Demo
- 9:13Why it wont work
- 13:39Expand Contract
- 18:07Summary
- 35:21Sending the new message type
- 37:13Changing the schema
- 39:47Recap
- 40:47Questions
related talks
30mExpand Contract Pattern for Continuous Delivery of Databases
41mSurviving Continuous Deployment in Distributed Systems
51mPatterns & Playbooks to Make Every Commit Production Ready
23mContinuous Deployment - The Last Frontier for Continuous Delivery
28mAutomate everything with CDK in AWS
01h 21mContract Driven Development-Deploy MicroServices Independently W/out Integration Testing
24m"Misadventures in Continuous Delivery"
37mDevelop and implement a successful DevSecOps approach