Hatching software development ecosystems (the gordian knot)
summary
DevOps adopters deploy up to 46x more frequently and achieve commit‑to‑deploy lead times up to 400x faster, while success correlates with loosely coupled bounded contexts as unit of responsibility. Microservices alone often worsen coupling and make refactoring an order of magnitude more expensive. Concrete cases: a high‑performing team loses autonomy when forced onto an external platform and all leave within six months; a bank service depends synchronously on 12 unreliable services, creating constant fear. Use autonomy/mastery/purpose, fast feedback loops and even‑storming to reveal workable boundaries.
AI-written summary · about
chapters (9)
- 0:00The impact of DevOps
- 4:02Microservices challenges
- 8:35Defining organizational culture
- 12:27Social dynamics and feedback
- 17:19Architectural pitfalls
- 20:24Motivation through purpose
- 30:24The importance of feedback
- 38:23Case studies in dysfunction
- 46:56Bounded context and unity
related talks
38mConway's law in practice: Agile teams & Microservises
39mKeynote - The gordian knot
47mMicroservices and the Inverse Conway Manoeuvre
29mDevOps Anecdotes
32mTales from the DevOps Transformation Trenches
30mAdopting DevOps? You are aiming at the wrong target!
01h 00mMicroservices and the Inverse Conway Manoeuvre
22mA Healthier Software Development Life Cycle with DevOps