From microservices to migroservices
summary
The talk examines why projects that start as microservices often devolve into “migroservices” — services that regain monolithic characteristics. It names practical problems encountered (service coupling, shared data, deployment/operations difficulty, unclear ownership) and analyzes the common pitfalls that cause microservices to accumulate monolith-like baggage, considering whether this regression can be a transitional step toward a healthier microservice architecture.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 10:49Microservices promises
- 13:54Migroservices concept
- 18:08Boundary problems and coupling
- 21:38Conway's law and organization
- 23:46Error handling and resilience
- 26:52Service communication
- 30:18Workflow modeling
- 32:02Operational costs and complexity
- 36:34Orchestration and automation
- 39:45Why microservices?
- 44:16Q&A
related talks
49mFrom Microservices to Migroservices
55mMicroservices, Where Did It All Go Wrong
44mMicroservices, Where Did It All Go Wrong
48mMicroservices - Opportunities, Dilemmas and Problems
38mFrom Monolith to Microservices
01h 00mMicroservices, Where Did It All Go Wrong?
32mMicroservices: A retrospective
01h 03mFrom Monolith to Microservices: Story and Practice