Define Cloud Computing
Visual slide deck that explains what cloud computing means, the five essential characteristics defined by NIST, service models (IaaS, PaaS, SaaS), and practical considerations.
Define Cloud Computing
Define Cloud Computing. One-sentence definition. 5 essential characteristics. Delivery model vs "using a browser". Practical scenarios + common pitfalls.
Define Cloud Computing
Define Cloud Computing. One-sentence definition. 5 essential characteristics. Delivery model vs "using a browser". Practical scenarios + common pitfalls.
Cloud computing
Cloud computing. On-demand delivery of computing services over a network using provider infrastructure. Services: Servers, storage, databases, networking, software. Network Delivery: Delivered over a network (often the internet). Provider Infrastructure: Provider runs infrastructure; you consume services. Payment Model: Pay-as-you-go is common, not defining.
Provisioning
Provisioning. Provisioning + scaling without owning hardware. What is Provisioning? Provision = create and make ready to use. Create via portal, Application Programming Interface (API), automation. Key Distinction: Scale without procurement or hardware ownership. Browser access ≠ delivery model.
National Institute of Standards and Technology (NIST)
National Institute of Standards and Technology (NIST). 5 essential characteristics. If a service fits these five traits, it matches the core cloud model. On-demand self-service. Broad network access. Resource pooling. Rapid elasticity. Measured service.
On-demand self-service
On-demand self-service. You can provision what you need, when you need it—without provider staff. 01 No Staff Interaction: Provision without provider staff interaction. 02 Fast Creation: Create resources in minutes. 03 Multiple Interfaces: Interfaces: portal, Command-Line Interface (CLI), Application Programming Interface (API). Important: Self-service ≠ auto-scaling.
Broad network access
Broad network access. Services are reachable over the network from many client types. Network Available: Available over the network. Multiple Devices: Works from laptops, phones, thin clients. Standard Access: Standard access mechanisms. Remember: Access method ≠ cloud definition.
Resource pooling (multi-tenant)
Resource pooling (multi-tenant). Shared provider capacity with logical separation between customers. Shared Pool: Shared pool of compute, storage, networking. Multi-tenant Model: Multi-tenant: many customers, one provider pool. Logical Separation: Logical separation between customers. Clarification: Pooling ≠ "everyone shares the same data".
Rapid elasticity
Rapid elasticity. Capacity can scale out and scale in quickly to match demand. Scale Out: Scale out for spikes, scale in when demand drops. Fast Changes: Fast changes in capacity (short lead times). Automation: Can be automatic. Note: Elasticity ≠ self-service.
Measured service
Measured service. Usage is metered for transparency, monitoring, and reporting. Metered Usage: Metered usage (monitor, control, report). Billing Model: Enables consumption-based billing. Transparency: Helps you see what you used. Important distinction: Measured ≠ "cheap" or "fixed price".
Cloud is about speed and flexibility
Cloud is about speed and flexibility. Agility is the core shift; cost can be a benefit. Speed: Provision in minutes, not weeks. Flexibility: Adjust capacity as needs change. Experimentation: Faster experimentation. Cost Perspective: Don't define cloud by cost alone.
Shared responsibility + IaaS/PaaS/SaaS
Shared responsibility + IaaS/PaaS/SaaS. Responsibility is shared, and the split changes by service model. SaaS (Software as a Service): customer manages least (config/users/data governance). PaaS (Platform as a Service): provider manages more platform. IaaS (Infrastructure as a Service): customer manages more. Key concept: Shared responsibility: provider vs customer.
Practical: browser vs 'need a VM today'
Practical: browser vs "need a VM today". Use the characteristics to interpret what a scenario is really saying. What Doesn't Define Cloud: Browser use is not a cloud definition. What Does Define Cloud: Look for provisioning + scaling without owning infrastructure. Real-World Examples: "Need a Virtual Machine (VM) today" → on-demand self-service. Expect metering → measured service.
Practical recap: spikes + IaaS
Practical recap: spikes + IaaS. Elasticity handles changing demand; IaaS doesn't remove customer responsibilities. Traffic Patterns: Traffic spike then normal → rapid elasticity. Scaling Speed: Scale out/in without long lead times. IaaS Reality: Infrastructure as a Service (IaaS) ≠ "provider manages everything". Customer Duties: Customer still manages apps, access, and data.
Common pitfalls
Common pitfalls. Most confusion comes from mixing up the internet, characteristics, and service models. Internet ≠ Cloud: Internet use ≠ cloud definition. Deployment Models: Cloud can be public, private, or hybrid. Self-Service vs Elasticity: Self-service ≠ rapid elasticity. Pooling Misconception: Resource pooling ≠ no isolation. Measured Service Reality: Measured service ≠ cheap/fixed.