UNIT–I: INTRODUCTION TO CLOUD COMPUTING

1. Definition and Core Idea of Cloud Computing

Cloud computing is a computing paradigm where IT resources (compute, storage,

networking, platforms, software) are delivered as services over the internet, provisioned on
demand, and billed based on actual usage.

Core transformation:

• Computing becomes a utility

• Infrastructure becomes programmable

• Capacity becomes elastic

Formal definition (NIST-based)

Cloud computing provides convenient, on-demand network access to a shared pool of
configurable computing resources that can be rapidly provisioned and released with
minimal management effort.

2. Why Cloud Computing Was Needed (Problem Statement)

2.1 Traditional On-Premise IT Model

Each organization:

• Buys its own servers

• Sizes infrastructure for peak load

• Maintains unused capacity most of the time

Analogy:
Each factory running its own power plant instead of using an electricity grid.

Problems:

• 80–90% servers idle

• Huge upfront CAPEX

• Long procurement cycles (weeks/months)

• Poor fault tolerance

• Difficult global expansion

2.2 The Vicious Cycle of Traditional IT

 1. Forecast peak demand (guesswork)

2. Buy fixed hardware

3. Over-provision → wasted money

OR
Under-provision → system crashes, lost users

4. Repeat cycle every year

Result:
High cost, low agility, slow innovation

3. Evolution of Computing (Step-by-Step)

3.1 Mainframe Era (1960s–1980s)

• Centralized computing

• Dumb terminals

• Very expensive systems

• Limited user access

Use case: Banking, defense, census

Limitation: No scalability, extremely high cost

3.2 Client–Server Era (1990s)

• Distributed systems

• Personal computers + servers

• Department-wise servers

Improvement:

• Better accessibility

• Lower cost than mainframes

Problem:

• Server sprawl

• Underutilization

• Complex maintenance
3.3 Virtualization Era (2000–2006)

What is Virtualization
A technology that allows multiple virtual machines (VMs) to run on a single physical
machine using a hypervisor.

Hypervisor role:

• Abstracts CPU, memory, disk, network

• Allocates resources dynamically

Types:

• Type-1 (Bare metal): VMware ESXi, Xen

• Type-2 (Hosted): VirtualBox

Impact:

• One server → many VMs

• Utilization increased from ~15% to ~60%

• Faster provisioning

Limitation:

• Still bound to physical data center capacity

3.4 Cloud Era (2006–Present)

Key leap:
Virtualization + Internet + Automation + Metered billing

Milestone:

• AWS EC2 (compute)

• AWS S3 (storage)

New abilities:

• Self-service infrastructure

• Global availability

• Elastic scaling

• No upfront investment

4. Fundamental Characteristics of Cloud Computing (Deep Dive)

4.1 On-Demand Self-Service

Meaning:
Users provision resources themselves without provider interaction.

Example:
A developer launches 10 virtual machines using AWS CLI in 30 seconds.

Exam angle:

• No manual approval

• API-driven infrastructure

4.2 Broad Network Access

Meaning:
Services accessed via standard networks and protocols (HTTP/HTTPS).

Example:

• Gmail accessed from laptop, phone, tablet

• Cloud APIs accessed from any country

Outcome:

• Global reach

• Device independence

4.3 Resource Pooling (Multi-Tenancy)

Meaning:
Cloud provider pools physical resources and shares them across customers.

Important concept:
Customers are logically isolated, not physically dedicated.

Example:
100 companies share the same data center, but cannot see each other’s data.

Benefit:

• Cost reduction

• Efficient utilization

4.4 Rapid Elasticity

Elasticity ≠ Scalability

Aspect Elasticity Scalability

Nature Automatic Planned

Time Immediate Long-term

Trigger Real-time demand Forecast

Example of elasticity:

• E-commerce site scales from 10 to 10,000 servers during sale

• Scales back after sale ends

4.5 Measured Service (Pay-Per-Use)

Meaning:
Usage is continuously monitored and billed.

Billing metrics:

• Compute: per second / per hour

• Storage: GB per month

• Network: data transferred

Example:
If a VM runs for 10 hours, you pay only for 10 hours.

5. Cloud Service Models (Responsibility Breakdown)

5.1 Infrastructure as a Service (IaaS)

Provider manages:

• Data center

• Hardware

• Virtualization layer

User manages:

• OS

• Middleware

• Runtime
 • Applications

• Data

Example:
Hosting a Linux VM on Amazon EC2.

Use cases:

• Legacy applications

• Lift-and-shift migration

• Maximum control environments

5.2 Platform as a Service (PaaS)

Provider manages:

• Infrastructure

• OS

• Runtime

• Auto-scaling

• Patching

User manages:

• Application code

• Data

Example:
Deploying a Spring Boot app on Azure App Service.

Benefit:

• Faster development

• No server management

5.3 Software as a Service (SaaS)

Provider manages everything.

User does:

• Login

• Configure settings
 • Use application

Examples:

• Google Docs

• Salesforce CRM

• Zoom

Trade-off:
Convenience vs customization

6. Cloud Deployment Models (With Scenarios)

6.1 Public Cloud

Ownership:
Cloud provider

Access:
Multiple customers

Example use case:

Startup launching a mobile app with unpredictable traffic.

Advantages:

• Lowest cost

• Fastest scaling

Disadvantages:

• Less control

• Shared security model

6.2 Private Cloud

Ownership:
Single organization

Deployment:
On-premise or hosted

Example:
Bank running core banking systems.

Advantages:
 • High control

• Regulatory compliance

Disadvantages:

• High cost

• Limited elasticity

6.3 Hybrid Cloud

Structure:
Private cloud + Public cloud

Typical pattern:

• Sensitive data on private cloud

• Web front-end on public cloud

Example:
Hospital stores patient records privately, uses public cloud for analytics.

6.4 Multi-Cloud

Structure:
Multiple public cloud providers.

Reasons:

• Avoid vendor lock-in

• Disaster recovery

• Best service per provider

Example:
AWS for compute, Azure for identity, GCP for analytics.

7. Major Cloud Providers and Ecosystem

7.1 Amazon Web Services (AWS)

• Market leader

• Widest service portfolio

• Strong IaaS and PaaS offerings

7.2 Microsoft Azure

• Strong enterprise adoption

• Best integration with Microsoft stack

7.3 Google Cloud Platform (GCP)

• Strength in AI, ML, analytics

• Kubernetes leadership

Market trend:

• Explosive growth due to AI workloads

8. Enterprise Cloud Adoption

8.1 Benefits

• No capital investment

• Faster innovation

• High availability

• Global scalability

8.2 Risks

• Data breaches

• Vendor dependence

• Compliance complexity

8.3 Challenges

• Cloud skill shortage

• Legacy system redesign

• Cost mismanagement

8.4 Success Factors

• Clear cloud strategy

• Governance and cost controls

 • Skilled cloud architects

9. Exam-Focused Summary Points

• Cloud = utility computing model

• Virtualization is the backbone

• Elasticity is the key differentiator

• IaaS, PaaS, SaaS differ by control level

• Hybrid and multi-cloud dominate enterprises

• Cloud adoption is strategic, not just technical

If you want, the next logical step is:

• Unit-I short notes

• 15–20 exam questions with answers

• MCQs

• One-page revision sheet