Cloud Computing Basics Explained (IaaS, PaaS, SaaS Guide)

Cloud computing is the delivery of computing services — servers, storage, databases, networking, software, and analytics — over the internet (“the cloud”) so organizations can rent instead of own their infrastructure.

What You’ll Learn

By the end of this tutorial, you’ll understand the three cloud service models (IaaS, PaaS, SaaS), deployment types (public, private, hybrid), key benefits like elasticity and pay-as-you-go pricing, and how to choose the right cloud model for your project.

Why Cloud Computing Matters

Cloud computing has transformed how software is built and delivered. Instead of buying servers and managing data centers, startups can launch globally in minutes. In 2026, over 90% of enterprises use cloud services. At DodaTech, DodaZIP and Durga Antivirus Pro run on cloud infrastructure for scalable threat detection and updates.

Cloud Computing Learning Path

    flowchart LR
  A[Cloud Basics] --> B[AWS]
  A --> C[Azure]
  A --> D[GCP]
  B --> E[Docker & Kubernetes]
  A --> F{You Are Here}
  style F fill:#f90,color:#fff
  

What Is Cloud Computing? (The “Why” First)

Think of cloud computing like renting an apartment vs buying a house. When you buy a house, you pay the full cost upfront, handle all maintenance, and manage repairs yourself. When you rent, you pay monthly, the landlord handles maintenance, and you can move when your needs change.

Cloud computing is “renting” for IT infrastructure:

• Traditional IT: Buy servers, install cables, manage cooling, hire staff, wait weeks for delivery
• Cloud IT: Click a button, get a server running in seconds, pay only for what you use

The Three Service Models

IaaS — Infrastructure as a Service

IaaS provides virtualized computing resources — servers, storage, networking — on demand.

Think of it as: Renting an empty apartment. You bring your own furniture (operating system, applications, data) and maintain everything above the basic structure.

Examples: AWS EC2, Google Compute Engine, Azure Virtual Machines

Best for: Organizations that need full control over their infrastructure. You manage the OS, runtime, and apps.

# Simulating an IaaS deployment
# You provision a virtual machine and configure it
instance_config = {
    "provider": "AWS",
    "service": "EC2",
    "os": "Ubuntu 24.04 LTS",
    "cpu": 4,          # vCPUs
    "ram_gb": 16,
    "storage_gb": 100,
    "hourly_cost": 0.12  # $ per hour
}

print(f"Provisioning {instance_config['cpu']}-core VM on {instance_config['provider']}...")
print(f"Cost: ${instance_config['hourly_cost']}/hour (~${instance_config['hourly_cost'] * 24 * 30}/month)")

Expected output:

Provisioning 4-core VM on AWS...
Cost: $0.12/hour (~$86.4/month)

PaaS — Platform as a Service

PaaS provides a platform to develop, run, and manage applications without worrying about the underlying infrastructure.

Think of it as: Renting a furnished apartment. Everything is set up — you just bring your clothes (code) and start living (deploying).

Examples: Google App Engine, Heroku, AWS Elastic Beanstalk, Azure App Service

Best for: Developers who want to focus on code, not server management. The platform handles scaling, load balancing, and monitoring.

SaaS — Software as a Service

SaaS delivers fully functional software applications over the internet, ready to use.

Think of it as: Staying in a hotel. Everything is provided, you just use it. You don’t manage anything.

Examples: Gmail, Google Docs, Salesforce, Microsoft 365, Slack

Best for: End users who need the software to “just work” without any setup or maintenance.

Comparison

Deployment Models

Public Cloud

Resources are owned and operated by a third-party provider and shared across multiple customers.

Pros: Lowest cost, no maintenance, instant scaling Cons: Less control, shared infrastructure (multi-tenant)

Example: AWS, Azure, GCP

Private Cloud

Resources are used exclusively by one organization, either on-premises or hosted by a third party.

Pros: Full control, high security, compliance-friendly Cons: Higher cost, requires maintenance

Example: OpenStack, VMware vSphere

Hybrid Cloud

Combines public and private clouds, allowing data and applications to be shared between them.

Pros: Best of both worlds, flexibility, cost optimization Cons: Complex management, requires careful integration

Example: AWS Outposts, Azure Arc, Google Anthos

Multi-Cloud

Using multiple public cloud providers simultaneously.

Pros: Avoid vendor lock-in, best pricing, redundancy Cons: Increased complexity, higher management overhead

Key Cloud Benefits

Elasticity

Scale resources up or down automatically based on demand. A website handling 100 visitors at night and 10,000 during a flash sale doesn’t need to pay for 10,000-capacity servers all day.

Pay-As-You-Go

Pay only for what you use, by the hour or even by the second. No upfront capital expenditure.

Global Reach

Deploy applications in data centers around the world. Users in Tokyo connect to a Tokyo data center, users in London connect to London — low latency everywhere.

Reliability

Cloud providers offer 99.9%+ uptime SLAs with redundant infrastructure across multiple availability zones.

Security

Cloud providers invest billions in security — more than most organizations can afford individually. However, security is a shared responsibility.

Shared Responsibility Model

┌─────────────────────────────────────────┐
│          YOU ARE RESPONSIBLE FOR         │
│  ┌─────────────────────────────────┐    │
│  │  Data, Applications, Access     │    │
│  │  Management, Network Config     │    │
│  ├─────────────────────────────────┤    │
│  │       CLOUD PROVIDER IS         │    │
│  │  ┌─────────────────────────┐   │    │
│  │  │ Physical Security,      │   │    │
│  │  │ Hardware, Networking,   │   │    │
│  │  │ Virtualization, Storage │   │    │
│  │  └─────────────────────────┘   │    │
│  └─────────────────────────────────┘    │
└─────────────────────────────────────────┘

Key insight: The cloud provider secures the infrastructure. You secure what runs on it — your data, access controls, and application code.

Common Cloud Mistakes

1. Assuming the Cloud Is Cheaper by Default

Cloud can be cheaper or more expensive depending on usage patterns. Predictable, steady workloads might be cheaper on dedicated servers. Always cost-compare.

2. Not Setting Budget Alerts

Without alerts, a misconfigured resource or DDoS attack can run up a massive bill. Set budget alerts from day one.

3. Ignoring the Shared Responsibility Model

Many breaches happen because customers didn’t secure their own data and access keys. The provider secures the cloud; you secure what’s in it.

4. Over-Provisioning Resources

It’s easy to provision large instances. Start small, monitor usage, and scale up based on real data, not guesses.

5. Vendor Lock-In

Using provider-specific services (like AWS Lambda or DynamoDB) makes migration harder. Architect for portability when possible.

6. Not Using Auto-Scaling

Manual scaling defeats the purpose of cloud. Configure auto-scaling rules based on CPU, memory, or request count.

7. Forgetting to Turn Off Dev Environments

Development and test instances left running 24/7 can cost more than production. Use scheduled shutdowns.

Practice Questions

1. What are the three cloud service models?

IaaS (Infrastructure), PaaS (Platform), SaaS (Software). IaaS gives you raw computing resources. PaaS gives you a deployment platform. SaaS gives you ready-to-use software.

2. What’s the difference between public and private cloud?

Public cloud is shared across multiple tenants (lower cost, less control). Private cloud is dedicated to one organization (higher cost, more control).

3. What is elasticity in cloud computing?

The ability to automatically scale resources up or down based on demand. This prevents over-provisioning (paying for unused capacity) and under-provisioning (running out of capacity during traffic spikes).

4. What does the shared responsibility model mean?

The cloud provider secures the physical infrastructure (servers, networking, data centers). The customer secures everything in the cloud (data, access management, application configuration).

5. Challenge: Estimate monthly cloud costs for a small web application serving 10,000 daily users.

Research current pricing: web server (t3.medium ~$30/month), database (db.t3.small ~$25/month), storage (50GB S3 $1/month), data transfer ($5/month). Total estimate: ~$60-80/month.

Mini Project: Cloud Cost Calculator

# cloud_cost_calculator.py
# Estimate monthly cloud costs for different configurations

def calculate_monthly_cost(service_type, cpu_cores, ram_gb, storage_gb, traffic_gb):
    """
    Estimate monthly cloud costs based on typical cloud provider pricing.
    """
    # Rough pricing estimates (USD/month)
    pricing = {
        "compute": {"per_core": 15, "per_gb_ram": 3},  # VM costs
        "storage": {"per_gb": 0.03},                     # Block storage
        "database": {"per_gb": 0.10},                    # Managed database
        "traffic": {"per_gb": 0.08},                     # Data transfer
        "load_balancer": 20,                              # Fixed LB cost
    }

    compute_cost = (cpu_cores * pricing["compute"]["per_core"] +
                    ram_gb * pricing["compute"]["per_gb_ram"])
    storage_cost = storage_gb * pricing["storage"]["per_gb"]
    traffic_cost = traffic_gb * pricing["traffic"]["per_gb"]
    lb_cost = pricing["load_balancer"] if service_type == "web" else 0

    total = compute_cost + storage_cost + traffic_cost + lb_cost
    return {
        "compute": round(compute_cost, 2),
        "storage": round(storage_cost, 2),
        "traffic": round(traffic_cost, 2),
        "load_balancer": lb_cost,
        "total": round(total, 2)
    }

# Example: Small web app
web_app = calculate_monthly_cost("web", 2, 4, 50, 100)
print("=== Small Web App ===")
for k, v in web_app.items():
    print(f"{k.replace('_', ' ').title()}: ${v}")

# Example: Data processing pipeline
pipeline = calculate_monthly_cost("batch", 8, 32, 500, 50)
print("\n=== Data Pipeline ===")
for k, v in pipeline.items():
    print(f"{k.replace('_', ' ').title()}: ${v}")

Expected output:

=== Small Web App ===
Compute: $42.0
Storage: $1.5
Traffic: $8.0
Load Balancer: $20
Total: $71.5

=== Data Pipeline ===
Compute: $216.0
Storage: $15.0
Traffic: $4.0
Load Balancer: $0
Total: $235.0

FAQ

Try It Yourself

Most cloud providers offer free tiers. Sign up for:

1. AWS Free Tier — 12 months free with 750 hours/month of EC2
2. Google Cloud Free Tier — $300 free credits for 90 days
3. Azure Free Account — $200 free credits for 30 days

Provision a free-tier virtual machine, connect via SSH, and run:

# After SSH into your cloud VM
uname -a
# Shows the Linux kernel version
df -h
# Shows disk usage
free -h
# Shows memory usage

This is the same process DodaTech uses to provision infrastructure for DodaZIP and Durga Antivirus Pro update servers — just at a larger scale.

What’s Next

What’s Next

Congratulations on completing this Cloud Computing Basics tutorial! Here’s where to go from here:

• Practice daily — Consistency is more important than long study sessions
• Build a project — Apply what you learned by building something real
• Explore related topics — Check out other tutorials in the same category
• Join the community — Discuss with other learners and share your progress

Remember: every expert was once a beginner. Keep coding!