Bang on. A friend I work with used to say "microservices are for scaling teams, not tech" which I liked. Even with monolith -> microservices I've seen it go wr

Bang on. A friend I work with used to say "microservices are for scaling teams, not tech" which I liked. Even with monolith -> microservices I've seen it go wrong. One Go application I worked on it would take a senior engineer a week to add a basic CRUD endpoint as the code had been split in to microservices along the wrong boundaries. There was a ridiculous amount of wiring up and service to service calls that needed done. I remember suggesting a monolith might be more appropriate, and was told it used to be a monolith but had been "refactored to microservices"... This type of stuff can literally kill early stage companies.