Loading content
Infrastructure-as-a-Service (IaaS) is a foundational cloud computing model that delivers virtualized compute, storage and networking resources on demand. It lets teams rent infrastructure instead of owning it, lowering capital expenditure and speeding provisioning. Common concerns include abstraction level, multi-tenancy, billing models and self-service APIs…
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.
Infrastructure as a service provides compute, storage, and networking as usable infrastructure while the provider operates the physical foundation.
The approach grew from virtualization and the need to deliver infrastructure flexibly according to consumption. NIST classifies IaaS as a cloud service model in which customers control operating systems and applications on supplied resources.
Rent an empty, connected apartment: the operator supplies the building and lines; you choose the furnishings, operating system, and applications.
The provider operates the data center, hardware, and virtualization.
Customers typically manage operating systems and software.
Resources follow demand.
IaaS speeds environment delivery and shifts investment into ongoing consumption. Responsibilities for security and cost must be explicit.
Where this building block is located in the topic model.
No structure path available.
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.