

Microservices, Where Did It All Go Wrong? • Ian Cooper, James Lewis & Kris Jenkins
10 snips Mar 14, 2025
In this enlightening discussion, Ian Cooper, a coding architect at Just Eat, and James Lewis, a software architect at Thoughtworks, dive deep into the world of microservices. They explore the complexities of microservices implementation, highlighting both triumphs and pitfalls. The duo emphasizes the importance of managing organizational dynamics and technical debt while transitioning to product-focused teams. They also tackle challenges in auditing these architectures, using real-world examples. Their insights advocate for a strategic, context-aware approach to software development.
AI Snips
Chapters
Books
Transcript
Episode notes
George Best Analogy
- Ian Cooper shared a George Best anecdote about being in a hotel room with Miss World and champagne.
- This story illustrates how things can go wrong despite seeming success, relating it to microservices.
Microservices Misconceptions
- Microservices' 'micro' aspect often gets misinterpreted, leading to confusion about implementation.
- The introduction of DevOps, containers, and Kubernetes further complicates the understanding of microservices.
Microservices at Pace
- Rapid organizational scaling necessitates quick decisions about software partitioning, often leading to later regret.
- These initial decisions are made under pressure and don't reflect microservices' core principles.