Loading content
Cloud providers are organizations that deliver on-demand computing resources and managed services over the internet, including virtual machines, storage, networking, and higher-level platform services. They shape infrastructure, operational models and cost structures and influence architecture, security and compliance. Selection requires evaluation of perfor…
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.
A cloud provider is an organization that delivers compute, storage, networking, and managed platform services over the internet.
Cloud providers became important as organizations moved away from owning and running all infrastructure themselves and instead consumed remote computing as an elastic service. The cloud model exposes shared, on-demand resources; NIST clarified its core characteristics as well as service and deployment models in 2011. Providers operationalize that model by packaging data centers, standard services, and operating processes so teams can use them without building the platform from scratch.
Think of a cloud provider as a three-layer utility system. The bottom layer contains data centers, networks, and storage. A control layer in the middle exposes provisioning and scaling through consoles, APIs, and automation. At the top, teams consume VMs, databases, Kubernetes, or other managed services. The provider handles capacity, redundancy, and standard operations; the customer chooses services, region, security rules, and cost model.
IaaS, PaaS, and SaaS determine how much infrastructure the provider manages and how much configuration the customer owns.
Security and operations are split between provider and customer; the boundary depends on the chosen service.
Geographic distribution affects latency, resilience, and data placement.
Console, CLI, and APIs trigger the creation, change, and removal of resources.
Provider-specific services can add value but may also make migration and switching significantly harder.
The concept matters in architecture, procurement, migration, and security decisions. Cloud providers can speed up delivery and reduce operational work, but they also introduce pricing complexity, service boundaries, data-residency questions, and lock-in. Highly regulated, latency-sensitive, or very specialized workloads may fit on-premises or hybrid setups better.
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.