This is a pretty critical point. The drum I tend to beat is that the positive read of microservices is that they make your code reflect your org chart. (If the

This is a pretty critical point. The drum I tend to beat is that the positive read of microservices is that they make your code reflect your org chart. (If they don't do this, and that usually resolves into developers each owning a bunch of microservices that are related concepts but distinct and are context-switching all the live-long day, you've created the reverse of a big ball of mud: you've created a tar pit. Companies used to brag to me when they had 250 microservices with 100 developers, and I don't think any of those companies are going concerns.)