Brownfields DevOps in Practice
summary
Argues brownfield teams can move to safe, frequent releases by doing specific engineering work: run a baseline gap analysis, consolidate to one code base, build once deploy many by externalizing environment config, assign a unique increasing version per compile, and measure production. Use automation and a pipeline that filters builds, tests and deploys; handle databases with migration scripts and transitional schemas compatible one version back. Cites Knight Capital’s $440M loss from a partial deploy, notes Octopus and LaunchDarkly as examples, and cites Facebook doing ~500 daily deploys.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 1:05Brownfields
- 3:24DevOps
- 3:37What is DevOps
- 6:30How do you do DevOps
- 6:46Gap analysis
- 7:07Evaluation
- 8:23Good State
- 8:53One Code Base
- 10:19Isolate Variations
- 10:36Example
- 12:09Externalize
- 14:57Versioning
- 16:32Metrics
- 17:31Getting to a good state
- 18:29Deploy without drama
- 18:58Stateless deployment
- 19:58Deployment to production
- 22:18Migration scripts
- 23:36Transitional deployments
- 24:05Version compatibility
- 25:12Practical example
- 26:38Stateless deployments
- 27:54Faster deployments
- 28:33Automation
- 28:50Knight Capital Group
- 31:07Manual Automation
- 32:24Pipelines
- 35:50Feature Flags
- 39:35Improving Cycle Time
- 40:13Culture of DevOps
- 41:31Silos
- 42:25DevOps Team
- 44:31Fix Next Time
- 45:28Avoid Silos
- 45:47Questions
- 49:16QA
related talks
44mI Deploy On Fridays
21mValue of DevOps Release Process in Data Teams
05mBrownfield DevOps
46mContinuous Deployment Workflows
01h 01mI deploy on Fridays (and maybe you should too)
30mBringing DevOps Success to Every App, Tool & Role in Your Org
33mSoftware development practices for companies that want to make an impact
34mYou only have to change one thing to do the DevOps