Microservices - How to create problems by solving problems?
summary
A five-person team splits a monolith into microservices, builds per-UI API gateways, registers services with a service registry and adds retries, then shifts purchase flow to asynchronous events so payment, invoicing and shipping become three decoupled blocks processed via a message broker. They try port-and-adapter and DDD selectively, find CQRS for read models reduces four-point failure to one, and discover every solution — gateways, registry, brokers, compensating actions — adds operational cost and new failure modes that require teams and processes to evolve.
AI-written summary · about
chapters (7)
- 0:00Introduction to microservices journey
- 3:42Initial excitement and technology choices
- 10:15Designing component boundaries
- 16:20Connecting UI with backend services
- 24:54Handling business process failures
- 35:59Querying data in microservices
- 42:07Costs and benefits of microservices
related talks
14mMonolith 2 MicroServices Houston we've got a problem
01h 00mMicroservices, Where Did It All Go Wrong?
55mMicroservices, Where Did It All Go Wrong
43mMicroMonolith - Top anti-patterns of distributed systems
36mMicroservices Lessons Learned
57mEmbracing Microservices
24mPatterns of Evolution from Monolith to Microservices
42mQ&A - Monolith to Microservices