Introduction to Cloud Computing

Learning Objectives

• Define cloud computing and identify its five essential characteristics (NIST model)
• Explain the three major service models — IaaS, PaaS, and SaaS — with real examples
• Compare public, private, and hybrid cloud deployment models
• Evaluate the benefits and trade-offs of moving workloads to the cloud
• Identify the major cloud providers and the categories of services they offer
• Recognize common security and cost considerations that come with adopting cloud infrastructure

Quick Answer

Cloud computing is the delivery of computing resources — servers, storage, databases, networking, software — over the internet ("the cloud") instead of running everything on hardware you own. A provider like AWS, Azure, or GCP owns and maintains giant data centers, and you rent exactly the capacity you need, scaling up or down on demand and paying only for what you use. It matters because it removes the upfront cost and lead time of buying physical servers, lets a two-person startup and a Fortune 500 company use the same world-class infrastructure, and makes it possible to build applications that automatically handle traffic spikes without anyone manually racking new hardware.

What is Cloud Computing?

Before cloud computing, if a company wanted to launch a web application, it had to buy physical servers, install them in a data center, wire up networking, and hire people to keep it all running — weeks of lead time and a large upfront cost, even before writing a line of application code. Cloud computing flips this: a provider owns the hardware, and you rent capacity over the internet, provisioning a server in minutes and paying only for the hours you use it.

Formally, the U.S. National Institute of Standards and Technology (NIST) defines cloud computing as a model for enabling on-demand network access to a shared pool of configurable computing resources (networks, servers, storage, applications, services) that can be rapidly provisioned and released with minimal management effort.

Key Characteristics

NIST identifies five characteristics that distinguish "the cloud" from simply renting a server from a hosting company:

• On-Demand Self-Service: You can spin up a virtual machine or a database at 2 a.m. by clicking a button or calling an API — no human at the provider needs to approve it.
• Broad Network Access: Resources are reachable over the internet from laptops, phones, and other services, not just from inside one physical building.
• Resource Pooling: The provider serves many customers ("tenants") from the same physical hardware using virtualization, dynamically assigning capacity where it's needed. This is what lets providers achieve economies of scale.
• Rapid Elasticity: Capacity can expand or shrink automatically to match demand — an e-commerce site can add servers during a flash sale and remove them the next morning.
• Measured Service: Usage is metered (CPU-hours, GB stored, requests served), so billing is precise and usage is visible to both provider and customer.

Why it matters: these five properties are exactly what a traditional, self-hosted data center struggles to offer simultaneously. A company can build its own servers, but it can't cheaply make them elastic on an hourly basis or pool them efficiently across thousands of other companies' workloads.

Common misunderstanding: students often think "cloud computing" just means "someone else's server" or "a website hosted online." Renting one dedicated server from a traditional hosting company for a fixed monthly fee is not cloud computing — there's no self-service elasticity or fine-grained metering. The defining feature isn't "not on my machine," it's on-demand, elastic, self-service access to pooled resources.

Deployment Models

Cloud characteristics can be delivered through different deployment models:

• Public Cloud: Infrastructure owned and operated by a third party (AWS, Azure, GCP) and shared across many customers over the public internet. Cheapest and fastest to start with.
• Private Cloud: Infrastructure dedicated to a single organization, either on-premises or hosted by a provider. Used when compliance or data sensitivity rules out shared infrastructure.
• Hybrid Cloud: A mix of private and public cloud, often used to keep sensitive data on-premises while bursting extra compute to the public cloud during peak load.

Real-world example: a hospital might keep patient records in a private cloud to satisfy HIPAA requirements, but run its public appointment-booking website on AWS (public cloud) — a hybrid setup.

Benefits of Cloud Computing

1. Cost-Effectiveness: Capital expenditure (buying servers) becomes operational expenditure (renting compute by the hour). A startup can launch without a six-figure hardware bill.
2. Scalability: Netflix can add thousands of servers during a new season's release weekend and shut them down afterward — something impossible with owned hardware on that timescale.
3. Reliability: Providers replicate data across multiple data centers ("availability zones"), so a single hardware failure doesn't take down your application.
4. Flexibility: Developers in different countries can access the same infrastructure and collaborate without shipping physical drives or hardware.
5. Speed to Market: Provisioning a database used to take weeks of procurement; in the cloud it takes minutes, which shortens the time from idea to shipped product.

Why it matters: these benefits explain why even large enterprises with existing data centers are migrating — the economics and speed advantage compound over time, especially for workloads with variable demand.

Limitation to know: cloud is not always cheaper. A workload that runs at 100% constant utilization 24/7 (like a stable, predictable internal batch job) can be cheaper on owned hardware over a multi-year horizon than paying a cloud provider's margin every month. Cloud economics favor variable, spiky, or unpredictable workloads.

Major Cloud Providers

The market is dominated by three "hyperscalers," each offering hundreds of services across compute, storage, databases, networking, and machine learning:

• Amazon Web Services (AWS) — market leader; EC2 (compute), S3 (storage), RDS (databases), Lambda (serverless)
• Microsoft Azure — strong in enterprises already using Windows Server and Active Directory; Azure VMs, Blob Storage, Azure SQL
• Google Cloud Platform (GCP) — strong in data analytics and machine learning; Compute Engine, BigQuery, Cloud Storage

Smaller providers like DigitalOcean, Linode, and Oracle Cloud target simpler use cases or specific niches (e.g., DigitalOcean for developers who want a simple, predictable interface).

Cloud Service Models (Preview)

Cloud computing is usually delivered as one of three service models, covered in depth in the next chapter:

1. Infrastructure as a Service (IaaS) — rent virtual machines, storage, and networking (e.g., AWS EC2, DigitalOcean Droplets). You manage the OS and everything above it.
2. Platform as a Service (PaaS) — rent a managed environment to deploy code without managing servers (e.g., Heroku, AWS Elastic Beanstalk).
3. Software as a Service (SaaS) — use a finished application over the internet (e.g., Salesforce, Office 365).

Real-World Applications

• Netflix streams video to over 200 million subscribers entirely on AWS, scaling encoding and delivery capacity with viewing demand.
• Airbnb runs its listing search and booking infrastructure on AWS, scaling around seasonal travel spikes.
• Spotify moved its entire infrastructure to Google Cloud to take advantage of GCP's data analytics tools for music recommendations.
• University students use cloud free tiers (AWS Free Tier, Google Cloud's $300 credit) to practice deploying real applications without buying hardware.

Cloud Security Considerations

Moving to the cloud shifts some, but not all, security responsibility to the provider. Key considerations every developer should understand:

• Data encryption — both at rest (stored data) and in transit (data moving over the network)
• Access control and identity management — using IAM (Identity and Access Management) roles instead of shared passwords
• Compliance and regulatory requirements — GDPR, HIPAA, and other regulations may dictate where data can physically live
• Disaster recovery and business continuity planning — even cloud providers have outages; a good architecture spans multiple availability zones

This topic is explored in depth, including the shared responsibility model, in the next chapter on Cloud Security and Privacy.

Career Opportunities in Cloud Computing

• Cloud Architect — designs the overall cloud infrastructure for an organization
• DevOps Engineer — automates deployment pipelines and infrastructure provisioning
• Cloud Security Specialist — focuses on securing cloud environments and meeting compliance
• Cloud Solutions Consultant — helps businesses choose and migrate to the right cloud services
• Site Reliability Engineer (SRE) — keeps cloud-hosted systems available and performant

Key Terms

Term	Definition
Cloud Computing	Delivery of computing resources (servers, storage, databases, software) over the internet on a pay-as-you-go basis
Elasticity	The ability of a system to automatically scale resources up or down to match real-time demand
Virtualization	Technology that lets one physical server run multiple isolated virtual machines, enabling resource pooling
Availability Zone	An isolated physical data center location within a cloud region, used for fault tolerance
IaaS	Infrastructure as a Service — rented virtual machines, storage, and networking
PaaS	Platform as a Service — a managed environment for deploying application code
SaaS	Software as a Service — a complete, ready-to-use application delivered over the internet
Hybrid Cloud	A deployment combining private (on-premises) and public cloud resources
Pay-as-you-go	A billing model where customers are charged only for resources actually consumed

Common Mistakes

1. Misconception: "Cloud computing just means my data is stored on someone else's computer." Why it's wrong: This ignores the defining characteristics — on-demand self-service, elasticity, and metered billing. A file backed up to a single remote server without any of those properties isn't "the cloud" in the technical sense. Correct understanding: Cloud computing specifically refers to an elastic, self-service, metered pool of shared computing resources — the storage location alone doesn't qualify it.

2. Misconception: "The cloud is always cheaper than owning your own servers." Why it's wrong: Cloud pricing includes the provider's margin. For steady, predictable, 24/7 workloads over several years, owned hardware can be cheaper. Correct understanding: Cloud economics are best for variable or unpredictable demand, fast time-to-market, and avoiding upfront capital costs — not automatically "cheaper" in every scenario.

3. Misconception: "Once my application is in the cloud, the provider is responsible for its security." Why it's wrong: Cloud providers operate under a shared responsibility model — they secure the underlying infrastructure, but customers are still responsible for configuring access controls, encrypting their own data, and patching their own application code. Correct understanding: Security is a partnership; misconfigured S3 buckets and weak IAM policies (customer-side mistakes) are among the most common causes of cloud data breaches.

Comparison and Connections

Aspect	Traditional On-Premises	Cloud Computing
Upfront cost	High (buy servers, build data center)	Low (pay-as-you-go)
Scaling speed	Weeks (procurement, installation)	Minutes (API call or console click)
Maintenance	Customer's IT team	Provider (for underlying hardware)
Elasticity	Manual, limited by owned capacity	Automatic, near-unlimited
Best for	Stable, predictable, long-term workloads	Variable, fast-growing, or uncertain workloads

Practice Questions

Recall

1. List the five essential characteristics of cloud computing as defined by NIST. Answer guidance: On-demand self-service, broad network access, resource pooling, rapid elasticity, measured service.
2. Name the three major public cloud providers and one flagship service from each. Answer guidance: AWS (EC2/S3), Microsoft Azure (Azure VMs/Blob Storage), Google Cloud Platform (Compute Engine/BigQuery).

Understanding 3. Explain why "resource pooling" is necessary for a cloud provider to offer elastic, on-demand capacity. Answer guidance: Pooling lets the provider share physical hardware across many tenants using virtualization, so unused capacity from one customer can be reassigned instantly to another — this is what makes near-instant elasticity economically possible. 4. Why might a hybrid cloud model be chosen over a pure public cloud model? Answer guidance: Compliance/regulatory requirements or data sensitivity may require some workloads to stay on-premises (private), while other, less sensitive or more variable workloads run in the public cloud for cost and scale benefits.

Application 5. A startup expects unpredictable traffic that could spike 50x during a viral marketing campaign. Should they buy physical servers or use a public cloud provider? Justify your answer. Answer guidance: Public cloud — rapid elasticity lets them scale up automatically for the spike and scale back down afterward, avoiding the cost of owning idle hardware most of the time. 6. A university research lab runs the exact same computational workload at 100% utilization every day, year-round, for five years. Would cloud or on-premises hardware likely be more cost-effective, and why? Answer guidance: On-premises may be cheaper long-term for constant, predictable, high-utilization workloads because the provider's pay-as-you-go margin adds up over years without benefiting from elasticity.

Analysis 7. Compare and contrast IaaS, PaaS, and SaaS in terms of how much a customer manages versus how much the provider manages. Answer guidance: IaaS — customer manages OS and up; PaaS — customer manages only application code; SaaS — customer manages nothing but usage/configuration. Control decreases and provider responsibility increases from IaaS to SaaS. 8. A company argues "moving to the cloud eliminates our security responsibilities." Evaluate this claim. Answer guidance: False — the shared responsibility model means the provider secures the underlying infrastructure, but the customer remains responsible for access control, data encryption choices, and application-level security; most real-world cloud breaches trace back to customer misconfiguration.

FAQ

1. Is cloud computing the same as "the internet"? No. The internet is the network that connects cloud data centers to users; cloud computing is the service model of renting computing resources over that network.

2. Do I need to know networking to understand cloud computing? Basic networking helps (IP addresses, DNS, HTTP), but you can start learning cloud fundamentals — like provisioning a VM or an S3 bucket — before deep networking knowledge.

3. What's the difference between a cloud "region" and an "availability zone"? A region is a geographic area (e.g., us-east-1), and each region contains multiple availability zones — physically separate data centers within that region — used for fault tolerance.

4. Can a small business realistically use the same cloud services as a company like Netflix? Yes — that's the point of cloud computing's democratizing effect. A student or small business can use the exact same EC2 instances or S3 buckets Netflix uses, just at a much smaller scale and cost.

5. Which cloud provider should I learn first? AWS has the largest market share and the most job postings, making it a strong first choice, but the core concepts (compute, storage, networking, IAM) transfer directly to Azure and GCP.

Quick Revision

• Cloud computing delivers servers, storage, databases, and software over the internet, on-demand and pay-as-you-go.
• NIST's five characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service.
• Three deployment models: public, private, hybrid.
• Three service models: IaaS (infrastructure), PaaS (platform), SaaS (software) — control decreases, provider responsibility increases from IaaS to SaaS.
• Big three providers: AWS, Microsoft Azure, Google Cloud Platform.
• Benefits: cost-effectiveness, scalability, reliability, flexibility, speed to market.
• Cloud isn't automatically cheaper — best for variable, unpredictable workloads; owned hardware can win for steady 24/7 loads.
• Security follows a shared responsibility model — the provider secures infrastructure, you secure your configuration and data.
• Elasticity depends on virtualization and resource pooling across many tenants.
• Career paths: Cloud Architect, DevOps Engineer, Cloud Security Specialist, SRE.

Related Topics

Prerequisites: Basic networking concepts (IP addresses, client-server model), basic understanding of servers and virtualization

Related Topics: Virtualization and Containers, Distributed Systems, DevOps and CI/CD

Next Topics: Cloud Service Models (IaaS/PaaS/SaaS in depth), Cloud Security and Privacy, Cloud Storage Solutions