But it's not about employees. It's about capabilities, and working backwards. eg look at datastores. If you can fit your data in postgres on a single (potent

But it's not about employees. It's about capabilities, and working backwards. eg look at datastores. If you can fit your data in postgres on a single (potentially really expensive!) computer, you probably need two or three of those computers for a primary plus a couple replicas and a DBA. Once you outgrow that, going distributed costs a team. There is a big elbow in the cost and headcount curve. Once you want a different specific capability beyond the standard distributed datastores, that costs multiple teams. Yet another big elbow in the cost and headcount curve. This happens on data stores, applications, translations, currency, etc etc etc. Imagine a Greek person with a Greek bank account driving Uber in France being paid with an American amex card.