Sorry if this stings a bit... We already sort of do this (without the bad bits) and have done since about 2001. This is a little buzzword filled and doesn't d

Sorry if this stings a bit... We already sort of do this (without the bad bits) and have done since about 2001. This is a little buzzword filled and doesn't deal with the system-level practicalities of enterprise architecture. It seems like an internal technical proposal written up to sell to the business rather than a practical discussion. Mind you, what can you expect from a CTO... Regarding practicalities, it's a royal pain in the arse managing component and messaging contract versioning between "tall" architectures like this. Also it doesn't work well with a SaaS model as the logical partitioning is more complicated with different isolation requirements for different clients. Complexity goes up O(log N). Synergistic partitioning is pretty obvious and doesn't require an essay. Keeping things within budget is about managing scope and coupling, that is all. Nothing new here.