My concern with this is embedded right in the article:<p><pre><code>    One of the benefits to the majestic monolith is
    that it basically presumes that the people who
    work on it also understand it.
</code></pre>
I don&#x27;t consider this a benefit, it is instead a substantial risk.  And it is something that is almost impossible to maintain indefinitely as software teams grow, companies merge, new platforms or partners emerge, etc.  The new developer tasked with understanding a monolith has a nearly insurmountable task compared to understanding a limited-scope service.  Ultimately I think software architecture is more usefully approached as strategies to prevent disaster rather than creating the opportunity for majesty.