When I say &#x27;architectural&#x27; there I mean that as in the underlying design. How the system is modeled and and what different objects and interfaces exist in that model.<p>Eg. Say you have a billing component in your system. You may have the same underlying billing component in either a monolith or as microservices. It may be a nicely decoupled in both cases (either existing as an independent module&#x2F;library in the monolith case, or as an independent service in the microservices case.)<p>The (potential) benefit that&#x27;s afforded from the microservices approach is not that there&#x27;s a better underlying design there, but that a single team or developer can properly take ownership of deploying, scaling, monitoring and managing the service, independently of the rest of the application. (Plus scope for partitioning and graceful partial failures vs whole system failures)