Microservices can work for low-latency workloads—if you design for it

Microservices can work for low-latency workloads if you design them that way. Over the years, many people have told me, “Microservices don’t work when you need low latency; use a monolith.” I get it; for many, this advice comes from negative experiences. When you break a monolith into multiple services, you’re replacing function calls with network calls. Those network calls introduce latency, and the more services you depend on, the slower the overall request becomes. But does that really mean microservices can’t be used for low-latency systems? No, and I say that from experience. I’ve spent a

• #design
• #work