⚙️ Azure Compute Overview

Introduction

Azure offers multiple compute services for different workload types. Understanding when to use each service is crucial for building scalable and cost-effective applications.

Key Learning Outcomes

By the end of this lesson, you'll understand:

• Azure compute service options

• When to use each service

• Pricing models and scalability

• Real-world scenarios and use cases

• Service comparison and selection criteria

Azure Compute Services

1. Virtual Machines (VMs)

Best For: Full OS control, legacy applications, complex workloads

Key Characteristics:

• IaaS - Infrastructure as a Service

• Full control over OS and runtime

• Pay per minute

• Manual or auto-scaling

Basic Usage:

# Create VM
az vm create \
  --resource-group myResourceGroup \
  --name myVM \
  --image UbuntuLTS \
  --admin-username azureuser \
  --public-ip-sku Standard

# Start/Stop VM
az vm start --name myVM --resource-group myResourceGroup
az vm stop --name myVM --resource-group myResourceGroup

2. App Service

Best For: Web apps, APIs, background jobs

Key Characteristics:

• PaaS - Platform as a Service

• Automatic scaling

• Built-in security

• Multiple language support

Basic Usage:

# Create App Service plan
az appservice plan create \
  --name myAppServicePlan \
  --resource-group myResourceGroup \
  --sku B1 \
  --is-linux

# Create web app
az webapp create \
  --resource-group myResourceGroup \
  --plan myAppServicePlan \
  --name myUniqueAppName

3. Azure Functions

Best For: Event-driven, serverless, variable load

Key Characteristics:

• Serverless

• Pay per execution

• Scales to zero

• Event-triggered

Basic Usage:

# Create function app
az functionapp create \
  --resource-group myResourceGroup \
  --consumption-plan-location eastus \
  --runtime node \
  --functions-version 4 \
  --name myFunctionApp

4. Container Instances

Best For: Docker containers, quick deployment

Key Characteristics:

• Runs containerized apps

• No Kubernetes overhead

• Pay per second

• Quick startup

Basic Usage:

# Run container
az container create \
  --resource-group myResourceGroup \
  --name myContainer \
  --image nginx \
  --cpu 1 \
  --memory 1

5. Kubernetes Service (AKS)

Best For: Complex microservices, orchestration

Key Characteristics:

• Managed Kubernetes

• Auto-scaling

• Multi-container management

• Enterprise support

Basic Usage:

# Create AKS cluster
az aks create \
  --resource-group myResourceGroup \
  --name myAKSCluster \
  --node-count 3

Comparison Table

Key Takeaways

• **Virtual Machines** provide maximum control

• **App Service** is best for traditional web apps

• **Azure Functions** scales to zero for cost efficiency

• **AKS** handles complex orchestration

• **Choose based on:** control needed, scaling requirements, team expertise

Next Steps

Dive deeper into your chosen compute service with dedicated lessons.