Loading content
Cloud service models (IaaS, PaaS, SaaS) define layers of responsibility and abstraction for delivering computing resources over the internet. They clarify control, operational tasks and typical use cases, guiding architectural decisions and vendor selection. The distinction influences security, compliance and integration patterns between provider and consume…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Cloud service models classify cloud offerings by which layers the provider operates and how much responsibility remains with the consumer.
As cloud computing spread, organizations needed a clear way to describe operational and responsibility boundaries: who supplies infrastructure, platform, and application, who maintains them, and who carries which risks? NIST SP 800-145 (2011) framed cloud computing as a model with three service models and established IaaS, PaaS, and SaaS as shared terms for that progression in control and operational effort.
Think of a stack of managed layers. IaaS provides the base of compute, storage, and networking. PaaS adds a managed runtime and development platform on top. SaaS then delivers the finished application. The higher you move in the stack, the less infrastructure work remains for the consumer, but also the less direct control is available.
Each model hides more technical detail behind a different operational layer.
The model defines which tasks the provider takes on and which remain with the consumer.
The provider supplies infrastructure; the consumer manages the operating system, runtime, and own software.
The provider also runs the platform so the team can focus on the application and data.
The application is fully delivered; the consumer mainly configures content, access, and usage.
These models support architecture, security, procurement, migration, and operations decisions. They make visible how much control, maintenance, and compliance effort stays in-house. It is important to separate service models from deployment models; more convenience usually means less direct control, less customization, and often more vendor dependence.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.