> but the design thinking and decomposition strategy required to create a good microservices architecture are the same as those needed to create a well structur

> but the design thinking and decomposition strategy required to create a good microservices architecture are the same as those needed to create a well structured monolith I don't think that this quite captures the utility of something like microservices. For example, if you split your frontend and backend into separate projects, then the barrier for entanglement becomes so much higher. Instead of just importing some frontend class for the backend, you're loading in stuff from a totally different project and making 2 coordinated patches for them. Doesn't that feel wrong somehow? The appeal of microservices (much like functional programming) comes from imposing restrictions that make dangerous things harder. Reducing the possibility of breaking your own rules on clean programming. (Disclaimer: I don't think microservices are worth it for smaller projects though)