Symptoms of a distributed monolith, and how we fixed our service boundaries
We split an order platform into eleven services and ended up with the costs of microservices and the coupling of a monolith. The symptoms that gave it away, lock-step deploys, a shared database and chatty call chains, how we measured them, and the boundary changes that fixed them.