
GOTO - The Brightest Minds in Tech 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
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.
Investment Bank Experience
- James Lewis described working in investment banks where rapid software changes were essential to seize opportunities.
- Building small, independent software pieces allowed for quick adaptation to new trading products.
Goldilocks Point
- Ian Cooper highlighted the Goldilocks point in microservices: balancing small services with inter-service dependencies.
- This optimal point minimizes coupling without excessive services, varying by business needs.





