>Organizational structure tends to reflect its products' structure.
This seems to me to be the real reason why you can achieve some measure of success with this pattern: you can align your architecture with your corporate political set up.
If there is dysfunction across team boundaries where trust and cooperation is low, you can help deal with that by creating a 'contract' across that organizational layer in the form of an API end point.
Nonetheless, there's no reason why that contract must be in the form of a networked API end point.
This seems to me to be the real reason why you can achieve some measure of success with this pattern: you can align your architecture with your corporate political set up.
If there is dysfunction across team boundaries where trust and cooperation is low, you can help deal with that by creating a 'contract' across that organizational layer in the form of an API end point.
Nonetheless, there's no reason why that contract must be in the form of a networked API end point.