Loading content
Cloud deployment models describe how cloud resources are provisioned and managed (public, private, hybrid, community). They influence architecture, governance, security, and operations. The concept guides decisions about hosting strategies, balancing cost, compliance, and scalability. It provides practical guidance for selecting models based on workload and…
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 organizes, connects, or makes decisions possible.
Cloud deployment models describe how cloud resources are organized and operated: public, private, hybrid, or community. They clarify responsibilities, isolation, and operational boundaries and shape architecture decisions.
Cloud deployment models became a distinct idea in early cloud-computing definitions, especially in NIST SP 800-145, which separates deployment models from service models and core characteristics. The practical problem is architectural placement: where operations, control, data sovereignty, and shared use sit in public, private, hybrid, or community environments.
Think of a spectrum of housing types: a public apartment building, your own house, a connected duplex, and a residence shared by a specific group. The application can run in all of them; what matters is who provides the infrastructure, how much the environments are shared, and where security and administration boundaries are drawn. The model is therefore an operating frame for location, access, and responsibility.
The way cloud resources are placed sets operational and responsibility boundaries.
The four basic forms differ mainly in sharing, coupling, and organizational control.
It defines which side controls infrastructure, platform, and operations.
More sharing often increases efficiency; more isolation increases control and predictability.
Rules for data location, access, and evidence influence the model choice.
The decision matters when workloads must be balanced against regulatory requirements, cost, latency, scalability, and existing infrastructure. Public cloud often provides more elasticity, private environments more control, and hybrid models combine both but add integration and operational effort. The model alone does not solve security or compliance; it shifts responsibilities and boundaries.
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.