Cloud Characteristics
For an IT environment to qualify as a cloud, it must exhibit a specific set of characteristics that enable the remote provisioning of scalable and measured resources. The greater the degree to which these characteristics are supported and utilized, the greater the value proposition of the platform.
The Six Characteristics
Section titled “The Six Characteristics”| Characteristic | Core idea |
|---|---|
| On-Demand Usage | Self-service provisioning, fully automated after configuration |
| Ubiquitous Access | Accessible from any device, anywhere, via standard protocols |
| Multitenancy & Resource Pooling | Shared infrastructure that keeps tenants isolated |
| Elasticity | Automatic, transparent scaling in response to runtime demand |
| Measured Usage | Pay only for what you use; built-in monitoring and reporting |
| Resiliency | Redundant implementations that failover automatically |
On-Demand Usage
Section titled “On-Demand Usage”Also called on-demand self-service usage — a cloud consumer can unilaterally provision cloud-based IT resources without requiring any human involvement from the cloud provider.
- Self-service: the consumer configures and activates resources through a portal, CLI, or API
- Fully automated: once configured, usage scaling and management requires no further manual interaction from either party
- Practical result: eliminating the provisioning bottleneck — new capacity appears in minutes, not days
Ubiquitous Access
Section titled “Ubiquitous Access”A cloud service must be widely accessible — not restricted to specific devices, locations, or network conditions.
To achieve this, cloud architectures must support:
- A variety of client devices — desktops, laptops, tablets, mobile phones, IoT devices
- Multiple transport protocols — HTTP/S, WebSocket, gRPC, and others
- Diverse interfaces — web UIs, REST APIs, SDKs, CLI tools
- Multiple security technologies — TLS, OAuth 2.0, API keys, mTLS
Multitenancy and Resource Pooling
Section titled “Multitenancy and Resource Pooling”These two characteristics are closely linked and together underpin the economics of cloud computing.
Multitenancy
Section titled “Multitenancy”Multitenancy allows a single instance of a software program or IT resource to serve multiple different consumers (tenants) simultaneously, while keeping each tenant completely isolated from and unaware of the others.
Resource Pooling
Section titled “Resource Pooling”Resource pooling builds on multitenancy and virtualization to aggregate large-scale physical and virtual IT resources into a shared pool that serves many consumers at once.
| Property | Detail |
|---|---|
| Dynamic assignment | IT resources are assigned and reassigned based on live consumer demand |
| Mechanism | Typically implemented through statistical multiplexing |
| Consumer view | Consumers perceive dedicated resources; actual allocation is shared |
Elasticity
Section titled “Elasticity”Elasticity is the automated ability of a cloud to transparently scale IT resources in response to runtime conditions — or based on thresholds predetermined by the consumer or provider.
- Automatic — no manual intervention required; the cloud monitors and responds to demand signals
- Transparent — consumers don’t see the underlying provisioning; they just see consistent capacity
- Proportional — scaling is tied directly to measured usage, which enables reduced upfront investments and pay-as-you-go cost models
- Range — the breadth of elasticity available depends directly on how large the provider’s IT resource pool is; larger pools offer wider scaling ranges
Measured Usage
Section titled “Measured Usage”Measured usage is the cloud platform’s ability to accurately track resource utilization and charge consumers only for what they actually use.
This characteristic has two dimensions:
| Dimension | What it means |
|---|---|
| Billing | Consumers pay only for the specific resources consumed, or for the exact timeframe they were accessed |
| Monitoring & Reporting | The platform continuously records usage data, which is valuable even in private clouds that don’t charge per use |
Measured usage is closely linked to on-demand usage — you can only charge for what you can measure, and you can only scale automatically if you know current utilization.
Resiliency
Section titled “Resiliency”Resilient computing involves preconfiguring redundant implementations of IT resources across physically separate locations so that failure is handled automatically — without requiring manual intervention.
| Scenario | How resiliency handles it |
|---|---|
| A resource instance fails | Processing automatically transfers to a redundant implementation |
| An availability zone goes down | Failover occurs across locations within the same cloud |
| A full cloud environment fails | Failover can occur across multiple different clouds |
The practical outcomes for consumers:
- Increased reliability — applications tolerate individual component failures
- Increased availability — systems remain accessible even during infrastructure events
Why All Six Matter Together
Section titled “Why All Six Matter Together”These characteristics are not independent — they reinforce each other:
- On-demand + elasticity → capacity is always right-sized without manual effort
- Measured usage + on-demand → costs track actual consumption, not reserved capacity
- Multitenancy + resource pooling → the economics work at scale
- Ubiquitous access + resiliency → the service is available anywhere, even during failures
An IT environment that lacks any of these characteristics is not fully cloud — it may be hosted infrastructure, managed hosting, or a private data center, but it doesn’t deliver the full value proposition of cloud computing.