In a medium-to-big organisation, similar tooling allow us to lead toward tech standardisation, a very important double-edged sword in the SOA or micro-services world...As you can imagine, this may be controversial because for many people, when we refer to S- we refer to cloud. In the previous example, if you run your infra in a self-managed data-centre (DC), you may have no cloud at all, but is that really relevant? ...In a 500 engineers organisation, isn't a self-managed DC a sort of cloud anyways? What I mean is that the devs that write the code that runs there, don't know all the details about the operational aspects and the cost-related matters...In fact, that code may go 30% on Azure, 60% on AWS and 10% on self-hosted DC depending on the config, and most devs don't really need to care. And I don't mean to be rude saying they don't need to care because they are not smart or stuff like that...