I think the article nails it on the head in the first paragraph >Change their database schema. >Release their code to production quickly and often. >Use deve

I think the article nails it on the head in the first paragraph >Change their database schema. >Release their code to production quickly and often. >Use development tools like programming languages or data stores of their choice. >Make their own trade-offs between computing resources and developer productivity. >Have a preference for maintenance/monitoring of their functionality. Every single one of those is an organizational problem. Microservices are fantastic for solving the problem of "very large organization trying to manage multiple releases from multiple teams with lots of interconnecting dependencies". But they solve that problem with a giant flaming chainsaw with greased up handle. It works but don't use it unless you have to.