Cloud Computing Foundations · Study deck
Cloud Computing: Origins and the NIST Model
"The cloud" is not a metaphor for a mysterious remote place.
Cloud Clara is your guide for this deck.
After studying this chapter
Learning objectives
Cloud computing combines a resource-sharing history with a specific model of service behavior.
- Cloud computing extends cluster, grid, and utility resource sharing.The ladder shows wider sharing, metered access, and rapid automatic allocation while physical hardware remains underneath the resource pool.
- The five essential characteristics describe observable service behaviour.An unattended virtual-server request can show self-service, while consumption reporting can show measured service in the chapter’s example.
- Characteristics, service models, and deployment models answer different questions.The framework distinguishes how the service behaves, which stack layers each party operates, and who shares or owns the resource pool.
- The component stack connects infrastructure to the clients using its services.Storage, platform, applications, and packaged services sit between raw computing resources and the end-user devices that consume them.
Major section
A cloud claim needs observable service behaviour
A rented server becomes part of a cloud claim only when the service has the required behavior.
- The cloud model provides access to a shared configurable resource pool.Servers, storage, networks, and applications can be shaped for a workload instead of being fixed resources that the consumer must own.
- Consumers can request resources on demand.The virtual-server example uses a web console at 2 a.m., without a provider employee manually handling the request.
- Self-service and elasticity change how capacity becomes available and is released.The service must support its required behaviour, rather than merely being a server administered by another organization.
- The definition is a model that can be checked across products.A rented server needs the essential cloud characteristics before the chapter’s cloud label is justified by observed service behaviour.
Major section
The cluster-grid-utility-cloud ladder
The evolution ladder adds broader sharing, metering, and automatic resource management.
- A cluster combines similar computing nodes into one system.The chapter describes homogeneous nodes working together, starting the ladder with shared resources an organization already owns.
- A grid can pool different nodes across a wider geographical area.Heterogeneous resources can be combined across distance for very large tasks, extending sharing beyond the cluster’s local starting point.
- Utility computing packages compute and storage for metered on-demand use.Resources can be purchased by the unit, making the shared computing capability available as a service with measured consumption.
- Cloud computing adds rapid automatic allocation and release.The resource pool can respond to demand with low management effort, even though real hardware still supports the apparently abundant capacity.
Major section
Shared hardware becomes a usable service
The historical mechanisms help explain how shared infrastructure became a usable service.
- Time-sharing lets several users use one mainframe’s resources.The chapter’s 1950s milestone shows shared computing before the later networked service model was established.
- Virtual machines can isolate tenants sharing one physical server.The 1970s milestone provides a mechanism for separating users while they depend on common underlying hardware.
- Expanding networks and VPNs can support access beyond the consumer’s site.The chapter’s 1990s milestone connects public networking and secure access to rented infrastructure outside the organization.
- Web-delivered business software is a concrete SaaS example.The 1999 Salesforce example is a concrete business application delivered over the web rather than installed as consumer-managed infrastructure.
Major section
The Five Essential Characteristics
Self-service and network access describe how consumers obtain the shared resources.
- On-demand self-service allows provisioning without a provider employee.A consumer requesting a virtual server at 2 a.m. can obtain resources without emailing someone and waiting for manual action.
- Broad network access uses standard mechanisms across varied clients.Phones, laptops, and tablets can reach the capabilities instead of depending on one proprietary client application.
- Resource pooling can assign shared capacity among multiple consumers.Physical and virtual resources can be assigned and reassigned as demand changes, making multitenancy part of the service behaviour.
- The consumer generally does not choose each resource’s exact physical location.The service offers a shared configurable pool, while the underlying hardware arrangement remains managed behind that access boundary.
Major section
Elasticity, metering, and the full definition
Elasticity and measurement connect changing demand with visible resource use.
- Rapid elasticity lets capacity expand and contract with demand.Resources can be provisioned and released as the workload changes, making the available capacity appear abundant to the consumer.
- Measured service monitors and reports the relevant consumption.Storage, processing, bandwidth, or active accounts can supply the metered quantity, depending on the type of service being reviewed.
- Unattended provisioning and usage-based billing show different characteristics.The 2 a.m. console request demonstrates self-service, while the server-hours and gigabytes in the bill demonstrate measured service.
- All five characteristics remain necessary when reviewing a cloud claim.A hosting arrangement missing one cannot satisfy the chapter’s NIST model merely because its vendor calls the service cloud computing.
Activity 1 · Match
✎ Name the cloud characteristic
I want you to match observable behavior to each part of the definition.
Match self-service, broad network access, resource pooling, rapid elasticity, and measured service to: reported consumption; unattended provisioning; shared capacity reassigned among tenants; standard access from varied clients; capacity expanding and contracting with demand.
3 minutes · Pen and paper · Answer: Activity 1
Major section
The three pillars and the component stack
The three pillars answer different questions about the same cloud service.
- Essential characteristics describe behaviour across every service model.Self-service, broad access, pooling, elasticity, and measurement are expected whether the consumer uses SaaS, PaaS, or IaaS.
- Service models define which stack layers each party operates.SaaS, PaaS, and IaaS can place the provider-consumer boundary at different layers while retaining the same essential cloud behaviours.
- Deployment models describe resource-pool sharing and infrastructure ownership.Public, private, hybrid, and community cloud are different deployment categories rather than substitutes for the essential characteristics.
- The component stack connects infrastructure through services to clients.Each layer can request what it needs from the layer below, connecting storage, platform, applications, and packaged services to end users.
Deck summary
Key takeaways
A cloud review combines behavior, management boundaries, and deployment context.
- Cloud computing adds rapid allocation and release to shared utility resources.The cluster-grid-utility-cloud ladder explains how sharing, metering, and automation combine in the final service model.
- The five characteristics can distinguish cloud service from ordinary external hosting.A remotely administered server still needs self-service, broad access, pooling, elasticity, and measurement to meet the chapter’s model.
- SaaS, PaaS, and IaaS define different provider-consumer boundaries.The essential characteristics remain applicable across those service models even though the user manages different parts of the stack.
- Layered components use services below instead of rebuilding every dependency.A browser or mobile client can use applications and packaged capabilities supported by platform, storage, and infrastructure layers underneath.
Retrieval practice
Recall check 1 of 3
Cloud Clara says: answer from memory, then check your reasoning.
Q1Where does cloud computing sit on the cluster-grid-utility-cloud evolution ladder, per the historical lineage this chapter traces?
Show answer
Answer: A Cloud computing is the most automated rung on a ladder that starts with cluster computing (shared local nodes), adds grid computing (distributed pooled nodes), adds utility computing (metered on-demand packaging), and finishes with cloud computing's rapid, automatic elasticity.
Retrieval practice
Recall check 2 of 3
Cloud Clara says: answer from memory, then check your reasoning.
Q2A company can request a new virtual server through a web console at 2 a.m. with no staff involved, and the bill is calculated from exactly how many server-hours and gigabytes it used. Which two NIST essential characteristics does this describe?
Show answer
Answer: A On-demand self-service means no human interaction is needed to provision; measured service means usage is metered and reported to both sides.
Retrieval practice
Recall check 3 of 3
Cloud Clara says: answer from memory, then check your reasoning.
Q3In the NIST three-pillar model, what is the relationship between essential characteristics and service models?
Show answer
Answer: A Essential characteristics are a cross-cutting precondition; service models and deployment models are two separate axes you choose independently on top of that precondition.
Print reference
Answers 1 of 2
Answer key.
- A · Cloud computing is the most automated rung on a ladder that starts with cluster computing (shared local nodes), adds grid computing (distributed pooled nodes), adds utility computing (metered on-demand packaging), and finishes with cloud computing's rapid, automatic elasticity.
- A · On-demand self-service means no human interaction is needed to provision; measured service means usage is metered and reported to both sides.
Print reference
Answers 2 of 2
Answer key.
- A · Essential characteristics are a cross-cutting precondition; service models and deployment models are two separate axes you choose independently on top of that precondition.
Print reference
Activity 1 answer
Model answer.
Match: Self-service: unattended provisioning. Broad network access: standard access from varied clients. Resource pooling: shared capacity reassigned among tenants. Rapid elasticity: capacity expanding and contracting with demand. Measured service: reported consumption.