Living in a Hybrid World
summary
Product page code moves from a monolith into microservices with CI/CD so the release cadence shifts from a five‑week batch to multiple releases per day, environments and data provisioning move to the cloud with automated config, and on‑call engineering ownership cuts mean time to detect and recover while producing fewer incidents. Deploys gain quick safety with rollback within minutes, the hardening window drops from two weeks to one and a 20% reduction target follows, and performance testing integrates earlier so there are no performance incidents since change.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:47How many Nordstrom customers
- 4:16Maturity
- 5:15Case Study
- 7:41OnCall Support
- 10:31Logging Metrics
- 12:47What Weve Learned
- 15:38Signoffs
- 18:05Autonomous but not fully autonomous
- 19:46You cant do everything at once
- 20:05The 5week release cycle
- 23:03The 2week release cycle
- 23:54Performance testing
- 25:17Leadership
- 26:50Questions
related talks
31mLiving in a Hybrid World
34mEnabling a Continuous Deployment Mindset
41mShift Left, Shift Right and Improve the Centre
26mDevOps and Lean in Legacy Environments
38mBuilding a high quality product
51mIt's a Small World After All
30mBuilding Applications in the Cloud: Best Practices
59mThe continuous culture