1.8 The three major providers, side by side
Describes the cloud landscape as of August 2026
What this is and why it exists
Job descriptions, syllabi and tutorials each assume one provider's names for the same handful of ideas. This lesson gives you the map: the three major providers, their shapes, and the translation table that lets you read all three while learning one deeply.
The vocabulary
- AWS (Amazon Web Services) — the oldest and broadest of the three, with the largest service catalogue.
- Microsoft Azure — strongest where organisations already live in Microsoft's estate; second by size.
- Google Cloud — smaller than both, with a reputation strongest in data and machine-learning services.
- Hyperscaler — a provider operating at global scale; these three are the ones the word usually means.
The mental model
One idea, three names. Underneath the branding, the providers sell the same conceptual catalogue, because the needs are the same everywhere. The translation table for the core ideas:
| The idea | AWS | Azure | Google Cloud |
|---|---|---|---|
| Rented virtual machine | EC2 | Virtual Machines | Compute Engine |
| Object storage | S3 | Blob Storage | Cloud Storage |
| Function, run on demand | Lambda | Functions | Cloud Run functions |
| Managed SQL database | RDS | SQL Database | Cloud SQL |
| Private network | VPC | Virtual Network | VPC |
| Identity and access | IAM | Microsoft Entra ID | Cloud IAM |
Learn one provider deeply — whichever your course, employer or project puts in front of you — and read the other two through this table. The concepts transfer whole; what changes is names, consoles and billing quirks. A person who understands what object storage IS can work in any of the three columns after a day of name-learning; a person who memorised one console cannot.
The smaller providers — regional clouds, Indian data-centre operators, specialist hosts — fit around the edges: closer support, local billing, sometimes local-law comfort. They matter in practice and appear in Indian job markets; the concepts you learn here apply to them unchanged. All three majors run regions in India.
What you should now be able to explain or do
Read a job description naming any provider's services and say what each service is in plain words. Name the typical strength of each of the three. Explain why learning concepts beats memorising one console.
Check yourself
A job advertisement asks for "S3 and Lambda experience". What are those, in plain words?
Object storage and on-demand functions — AWS's names for them. Azure and Google Cloud sell the same two ideas under different names.
What is each major provider's typical strength?
AWS — breadth and maturity of the catalogue; Azure — fit with organisations already on Microsoft; Google Cloud — data and machine-learning services.
Why learn one provider deeply instead of all three shallowly?
The concepts transfer and the names do not matter much — deep understanding of one column plus the translation table reads all three; three consoles memorised shallowly reads none.
Where do smaller and Indian providers fit?
Around the majors — local billing, closer support, local-law comfort. The same concepts apply to them unchanged.
Go deeper
We haven't checked most of these for screen reader use yet.
Back to The three major providers, side by side: work through the checklist