Improving Your Services the DevOps Way
summary
A mail infrastructure migration is rebuilt in parallel to the old system using a rolling upgrade that progressively replaces services. The team uses configuration management, writes configuration tests that run in production, and gradually ramps real traffic with an MX inbound 50% traffic split; they deploy upgraded packages, reuse templates or flat files where appropriate, and measure operations (config rollout averages 2.5 minutes) to achieve a resilient, reproducible infrastructure while continuing fixes during the rollout.
AI-written summary · about
chapters (9)
- 0:00DevOps methodology
- 3:50Mail infrastructure issues
- 7:09Config management need
- 10:23Engaging teams and avoiding tech debt
- 13:14Simplifying with bricks and templates
- 17:12Testing with real traffic
- 20:48Policy versus config
- 23:18Results and benefits
- 25:07Conclusion
related talks
35mPerforming Infrastructure Migrations at Scale
23mDevOps and Legacy Code
44mBreaking a Monolithic Devops
43mAbout to Start Your Nth DevOps Transformation?
29mTaming the Hybrid Beast with DevOps
33mThe Road to Enable DevOps Within the Payment Industry
24mWar Stories About the Ops in DevOps
25mMass migrations to the cloud