Developer Voices MicroServices For Better And Worse (with Ian Cooper and James Lewis)
Nov 14, 2024
Ian Cooper, a software architect at Just Eat, and James Lewis, a Thoughtworks expert and microservices pioneer, dive into the complexities of microservices architecture. They reflect on over a decade of experiences, questioning the initial hype and the enduring challenges of defining microservice boundaries. Key discussions include adapting to rapid growth, the Goldilocks point concept, and the philosophical implications of resilience. They also explore how financial incentives impact recruitment and branding in the software engineering field.
AI Snips
Chapters
Books
Transcript
Episode notes
Microservices: Early Misunderstandings Hurt
- Microservices often suffer from misunderstandings and rushed decisions made during rapid scaling phases.
- These early mistakes lead to regrets but also valuable lessons for improving microservice adoption.
Focus on Replaceability, Not Size
- Prioritize replaceability over simply smallness when defining microservice boundaries.
- Design microservices to evolve easily as the business changes, avoiding monolithic entanglement.
Fund Microservices as Products
- Use product team funding instead of project funding to allow microservices to evolve boundaries.
- Support continuous adjustment of service boundaries without waiting for new projects.
