3. Cloud Service Models¶
"Cloud" just means someone else's computer, rented over the internet. Which layers that someone else manages for you, versus which layers you manage yourself, is what separates the three service models.
| Model | You manage | They manage | Example |
|---|---|---|---|
| IaaS (Infrastructure as a Service) | The OS, software, everything on top | The physical hardware, virtualization, networking | A rented virtual server — hermes, the server this course wiki is built on, is exactly this |
| PaaS (Platform as a Service) | Just your application/code | The OS, runtime, and infrastructure underneath it | A service where you upload code and it just runs, with no server to configure |
| SaaS (Software as a Service) | Nothing but your own data and settings | Literally everything else | Gmail, Google Docs, Netflix |
As you move down that table, you give up control in exchange for not having to manage it — there's no "best" layer, only the right trade-off for what you're actually trying to do.
Try it
Classify each of these as IaaS, PaaS, or SaaS, and explain your reasoning: hermes (where this wiki's source lives), a Gmail account, a rented bare server you install your own OS onto.
Tip
"As a Service" always means the same pattern: whatever you're paying for, everything underneath that layer becomes someone else's problem, not yours.
Play it
Open the Virtualization and Cloud Lab and use the Service models tab.
Watch along
From the CompTIA A+ 220-1201 Full Course: Cloud service models (7:46:40)