Topic lessonTopic: Cloud foundations
What is cloud computing? Services, deployment and responsibilities
Cloud computing provides computing resources over a network, with on-demand provisioning and measured use. It changes how resources are obtained and managed, rather than merely moving a server elsewhere. Follow a document-sharing example to distinguish what a service provides from the work its customer retains.
Explain the defining features of cloud computing, distinguish IaaS, PaaS and SaaS by management scope, and identify the questions to ask before adopting a service.
No provider account or product knowledge is needed. Think of an application as software that processes requests, stores data and communicates with users.
Focus on how resources are provided
The US National Institute of Standards and Technology (NIST) identifies on-demand self-service, broad network access, resource pooling, rapid elasticity and measured service. A remotely hosted server alone does not explain the model. The available controls and the time needed to change capacity depend on the service.
- Requested capability → Service interfaceThe customer chooses a purpose and capacity; demand is not a reason for unlimited growth.
- Service interface → Resource poolThe service allocates resources. Isolation arrangements depend on the offering.
- Resource pool → Measured useMeasured use does not guarantee lower cost or a purely usage-based contract.
- Requested capability
- Identify the processing, storage and communication needed for document sharing.
- Service interface
- Use the capabilities exposed through a service interface.
- Resource pool
- The provider manages pooled computing resources.
- Measured use
- Usage is measured; applicable charges still depend on the offering.
IaaS, PaaS and SaaS describe the service boundary
IaaS means Infrastructure as a Service; PaaS means Platform as a Service; SaaS means Software as a Service. Use the table to compare the provided capability and the work retained by the customer.
| Model | What is provided | Customer decisions |
|---|---|---|
| IaaS | Infrastructure such as virtual machines, storage and networks | Operating systems, applications, data and access settings |
| PaaS | A platform on which to deploy an application | Application code, configuration, data and access |
| SaaS | A usable application | Users, sharing, configuration and the data entered |
Deployment models answer a different question
A service model describes the capability supplied. A deployment model describes how a cloud is constituted and for whom. Public clouds serve open use; private clouds serve one organization; hybrid clouds combine distinct cloud infrastructures. Private does not necessarily mean on premises, and public does not mean that customer data is publicly readable.
For an internal document service on a public cloud, the audience still needs its own access design. Do not read a deployment label as a file-sharing setting.
Worked example: a document-sharing service
| Need | Possible approach | Questions to resolve |
|---|---|---|
| Use collaborative editing soon | Consider a document-sharing SaaS product | Identity, sharing, export and exit arrangements |
| Build a custom approval workflow | Consider deploying an application on PaaS | Supported runtimes, deployment, access and retention |
| Control the operating system | Consider an application on IaaS virtual machines | Who will maintain the OS, application, capacity and recovery? |
Choose an option to see the result and explanation.
Before adoption: cost, data and ownership
- Define users, data and required control.
- Identify the provider boundary and assign the remaining operational work.
- Read billing units, fixed charges, transfer and exit conditions.
- Check access, storage location, retention, deletion and recovery needs.
- Evaluate a small scope before increasing use.
This lesson does not determine a product’s price or legal suitability. Next, review operating-system and networking foundations, then study the service boundary of a chosen provider.
Check, then explain in your own words
- Explain cloud computing beyond “a server somewhere else.”
- Separate service models from deployment models.
- Identify the data and access decisions in the document-sharing example.
Check your understanding: Does SaaS remove all customer-side management?
No. Users, sharing and the data entered still require decisions.
Receiving a managed application does not settle how your organization should use it or govern its data. Check the actual configuration and responsibility boundary of the service.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
Scope and conditionsSections 2–3: essential characteristics, service and deployment models. General definition, not current product pricing or a compliance determination.
Used in this lessonFocus on how resources are provided IaaS, PaaS and SaaS describe the service boundary Deployment models answer a different question