> least-overhead > well-defined APIs That's where most shifts to microservices fail, right? Sometimes because they don't define their APIs well, sometimes bec

> least-overhead > well-defined APIs That's where most shifts to microservices fail, right? Sometimes because they don't define their APIs well, sometimes because the breakdown into packages/services is broken (for example: defined by company structure instead of sane software architecture), sometimes because the evolution of each package's features and functionality is at odds with the stability of their API's semantics and guarantees (and documentation), sometimes because the development overhead of communicating between APIs is too high (debugging for example)...