Pragmatic DevOps
summary
Company moves from three apps to many microservices on AWS, builds automated self-service provisioning with Ansible (moved away from Puppet), and uses Jenkins for periodic synthetic smoke tests; a platform roadmap prescribes supported profiles for each practice. A prescriptive microservices maturity model assigns levels per service by risk and requires things like circuit breakers at level 3 and chaos engineering at level 4. Prioritizing critical services pays off — a sale at 3x traffic succeeds — but organizationwide 80% test coverage efforts repeatedly fail.
AI-written summary · about
chapters (5)
- 0:00Start
- 14:18Engineering practices get adopted faster when there is a clear execution plan with outcomes attached.
- 16:00Reality will push you to prioritize if you don't. This applies to adopting engineering practices as well.
- 17:45Every team is at a different journey. Different practices are needed for different teams and systems.
- 18:53It's all about controlling entropy. Bad choices cannot be the path of least resistance.
related talks
30mMoving beyond DevOps with automated cloud-native platforms
47mDevops, microservices and platforms, oh my!
21mDevOps Culture at Amazon
48mDevops@Scale
52mDevops @Scale
27mDevOps in the Cloud
31m10 Enterprise Tips for DevOps Success
01h 02mTransforming IT pros to DevOps gurus: Ssecure your new tech stacks