Architecture LineLesson
Microservices: what the network costs
Checkout's services can now ship on their own — but placing an order crosses four network hops and needs five services up at once. Why is it slower and less available than before, how do timeouts, breakers and queues keep one slow service from holding every checkout, and when is the whole thing not worth it?
17 minMediumStation: MicroservicesMembers lesson
Membership isn’t open yet. The free lessons are open — 18 of them.
- Modular monolith
- Service boundaries
- Microservices
What you'll be able to do
- 1Predict how latency and availability change when one in-process checkout call becomes a chain of synchronous service calls — delays add per hop, availabilities multiply.
- 2Explain how timeouts, circuit breakers and moving work onto a queue keep one slow service from holding up every checkout.
- 3Explain the operational prerequisites for microservices — fast provisioning, monitoring, automated deployment — and the premium a team pays before the benefits arrive.
- 4Choose between a (modular) monolith and microservices for a team from its size, how well the domain is understood and which parts truly need to release, scale or fail separately.
Inside the lesson
- steps
- 15
- questions
- 12
- simulations
- 0