it is not about it being hard. It simply creates effort to coordinate. And this effort needs to be considered. If you do things externally that means there is two PMs to pay, you need QMs on both sides, you need two legal/contract teams, you need to pay someone in procurement and someone in sales…

I agree with you that doing software inhouse when there is good options on the market is usually not a good idea. But for infrastructure i don’t see there to be as much of an efficiency loss. Especially as you very much need experts on how to set things up in a cloud environment and you better look carefully at how many resources you need to not overpay huge amounts.

If you are a small company then yes. But i would argue that for larger companies this doesn’t hold true. If you have 200 employees you’ll need an IT department either way. You need IT expertise either way. So having some people who know how to plan, implement and maintain physical hardware makes sense too.

There is a breaking point between economics of scale and the added efforts to coordinate between your company and the service provider plus paying that service providers overhead and profits.

And we should also consider the longevity of these infrastructures. Cities that built their subways in the 19th century are still running them today and are vastly superior in terms of transit abilities than car cities. The population densities of today are unimaginable without central sewers and water infrastructure. Having continent spanning electricity grids are gigantic achievements. All these have shaped our lives for decades and sometimes centuries already and they are set to do so for centuries to come.