Multi-cloud is the operational reality for most large organisations — they use AWS for primary workloads, Azure for Microsoft ecosystem integration, and GCP for data analytics and ML. A cloud engineer who can provision infrastructure on any cloud using Terraform (cloud-agnostic IaC), manage costs across clouds, and make principled cloud-selection decisions is significantly more valuable than one who knows only one provider deeply. Terraform's provider model abstracts cloud-specific APIs behind a consistent HCL (HashiCorp Configuration Language) syntax, enabling engineers to apply the same IaC workflow across AWS, Azure and GCP without learning three separate IaC tools.
Analogy🏏Cricket
🏏 Think of it like cricket: The match itself is the kernel — real computation at the hardware level. The commentators translating that action into words for the audience are the shell: they take raw events and present them in a form humans can understand and interact with. The television set in your living room is the terminal emulator: it displays the commentary but does not participate in the match.Just as switching from one broadcaster to another changes commentary style but not the underlying match, switching between Linux distributions changes shell defaults and package manager but not the kernel. Just as Star Sports and Sony Six both cover the same IPL match with different graphics packages, Ubuntu and Alpine both run the same kernel with different userspace tools.The insight is that these layers are genuinely separate, which is why you can swap any one of them independently.