More Alike Than Different

The three clouds look like rivals with completely different products. Browse their catalogs for five minutes and you'll find hundreds of services with unfamiliar names. It can feel like each one is a separate world that requires its own full education.

It isn't. Underneath the different names and logos, all three clouds offer the same handful of core building blocks — the same categories of service, solving the same fundamental problems. One of the most useful things you can learn about the cloud field is this: learning the concepts once transfers to all three providers. The names are just a lookup table.

Think about it the way you'd think about kitchens in different countries. The appliances have different brands and the controls might be labeled in a different language — but a stove is still a stove, a fridge is still a fridge, and someone who knows how to cook can work in any of them. The layout is the same; only the labels differ.

The Shared Core

Every major cloud provider offers the same foundational categories of service. Compute — computers to run software on. Storage — places to keep files and data. Databases — organized data stores for applications to read and write. Networking — the virtual wires and routers that connect everything together. Identity and access — the system that controls who can do what. All three clouds have all of these. Not as optional extras — as the core of what they sell.

Different Names, Same Idea

The clearest example is the virtual machine — a rented computer you can run your software on. AWS calls theirs EC2. Google Cloud calls theirs Compute Engine. Azure simply calls theirs Virtual Machines. Three different names; one idea. The same pattern holds across every category: a managed relational database — one where the provider handles the maintenance — is called RDS on AWS, Cloud SQL on Google Cloud, and Azure Database for PostgreSQL (or Azure SQL for Microsoft's own database engine) on Azure.

You will sometimes encounter a name you don't recognize. The right reflex isn't to panic — it's to ask "what category does this fall into?" Almost always the answer maps to something you already understand.

Why They Converge

The three clouds keep arriving at the same core offerings because they solve the same customer problems. If one provider introduces a useful service — say, a managed message queue — the others study it, build something equivalent, and compete on execution. They copy each other's good ideas constantly. The result, over fifteen years of competition, is a surprisingly similar set of core building blocks wrapped in three different sets of names and interfaces.

What This Means for You

This is the load-bearing idea for the rest of the course: learn the concept once and you've learned it everywhere. When a later chapter covers virtual machines, databases, or object storage, what you learn applies to AWS, Google Cloud, and Azure — and to smaller providers too. The provider-specific names are details you can look up. The underlying concepts are what you actually need to carry in your head.