Not every server connected to the internet qualifies as "Cloud Computing." For a system to be formally classified as a true cloud platform under international engineering standards, it must strictly satisfy the 5 Essential Characteristics established by the National Institute of Standards and Technology (NIST SP 800-145). Understanding these five pillars is mandatory for university examinations and cloud certification tests alike.
A consumer can unilaterally provision computing capabilities—such as server compute time, network storage, and database instances—automatically as needed, without requiring human interaction with the service provider's staff. You log into a web console, run a CLI command, or make a REST API call, and the resource is allocated within seconds.
Cloud capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms. This includes mobile smartphones, tablets, laptops, workstations, and IoT edge devices using standard protocols like HTTP, HTTPS, SSH, and WebSockets.
The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a degree of location independence: the customer generally has no control or knowledge over the exact physical location of the provided resources (e.g., specific server chassis or motherboard rack), but can specify location at a higher level of abstraction (country, region, or Availability Zone).
Capabilities can be elastically provisioned and released—in some cases automatically—to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. If traffic triples during a live broadcast, additional servers spin up instantly; when traffic subsides, excess servers terminate automatically.
Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
How can multiple competitive companies (for example, two competing banks) safely run workloads on the exact same physical server hardware? This is achieved through hypervisor-level hardware virtualization and cryptographic micro-segmentation:
| Layer | How Isolation is Guaranteed in Multi-Tenant Clouds |
|---|---|
| CPU & Memory Isolation | Hardware virtualization extensions (Intel VT-x, AMD-V) enforce memory page boundary separation. One virtual machine cannot access physical RAM addresses assigned to another tenant. |
| Virtual Network Isolation | Geneve / VXLAN encapsulation wraps tenant packets inside isolated Virtual Private Cloud (VPC) overlays. Traffic from Tenant A is invisible and physically unroutable to Tenant B. |
| Storage Isolation | Cloud block storage disks are encrypted with customer-specific Key Management Service (KMS) cryptographic keys. Data deallocation writes zeroes to physical sectors before reassignment. |
Question: "What is the difference between Scalability and Elasticity in cloud computing?"
Answer: Scalability is the system's architectural ability to handle increasing workload by adding resources (e.g., moving to a bigger database server). Elasticity is the system's ability to automatically adapt capacity in real-time—scaling outward during demand surges and scaling inward when traffic drops, matching resource consumption dynamically to real-time workload.
Broaden your enterprise cloud architecture and DevOps expertise across our curriculum:
Understand how elasticity and measured service are applied across virtual machines, platforms, and SaaS apps.
How cloud platforms dynamically scale horizontal computing capacity to maintain rapid elasticity.
Leverage measured service metrics, reserved instances, spot pricing, and billing budgets to control expenses.
Troubleshoot elasticity bottlenecks, capacity limits, and auto-scaling thrashing under traffic spikes.