Big microservices, small team a painful story

on YouTube ↗51m

" summary

Company migrates a monolith into dozens of business-capability services over seven years, then loses 80% of developers after a buyout and must run everything with one team. The team keeps services independently deployable with CI, Octopus Deploy, Cake, Sonar and library-scans, tracks ~160 services and platform state in a spreadsheet, and ports libs to .NET Core/.NET 6. Key pain: leftover legacy code and diverse pipelines — lesson: remove old code and standardize deploys.

AI-written summary · about

" chapters (13)

1. 0:00Introduction and speaker intro
2. 1:08Journey from guerrilla SOA to microservices
3. 8:24Conway's law and business capabilities
4. 12:41Company sold and team collapse
5. 15:52Reverse Conway's law and team restructuring
6. 19:05Surviving with a single team
7. 23:54Focus on single business capability
8. 27:45Diverse codebases and technical debt
9. 34:27Tracking system state and documentation
10. 41:38Current state and future steps
11. 42:19Q&A: Defining business capabilities
12. 45:04Q&A: New vs. fixing old code
13. 47:56Q&A: Codebase diversity trade-offs

" related talks

• 35mSeven years with microservices: a critical reviewPetr Kozelek · DevConf.CZ 2025
• 01h 01mMicroservices Gone WrongAnthony Ferrara · PHP UK Conference 2019
• 48mMicroMonolithMichal Franc · Codemotion Amsterdam 2017
• 29mMoving from A and B to ~150 microservices, the journey and learningsGeshan Manandhar · Container Camp AU 2019
• 48mThirty months of microservicesSander Hoogendoorn · Codemotion Milan 2016
• 53mSolving technical debt of a microservices architectureVaidas, Donatas · Build Stuff 2017
• 54mFrom a distributed monolith to a microservices solutionJan de Vries · NDC Sydney 2020
• 23mOn the road from Monolith to MicroChristoph Moser · WeAreDevelopers Conference Vienna 2016