Scenarios

Real workloads combine services, and a tier is only met when every component in the architecture meets it — the weakest link sets the ceiling. Pick a scenario to see the rolled-up gap.

Three-Tier Web App (PaaS)

A standard App Service front end backed by Azure SQL, with static assets on Storage and Load Balancing in front for regional failover.

App Service · Azure SQL Database · Storage Account (Blob / Files / Queue / Table) · Load Balancer / Application Gateway / Front Door · Key Vault

Microservices on AKS

Containerized services on AKS talking to Cosmos DB, decoupled by Service Bus, with Redis for session/cache state.

Azure Kubernetes Service (AKS) · Azure Cosmos DB · Service Bus · Azure Cache for Redis · Key Vault

IaaS Lift-and-Shift

VM-based workload migrated as-is, fronted by a load balancer, connected on-prem via a network gateway, protected by Backup & Site Recovery.

Virtual Machines / VMSS · Load Balancer / Application Gateway / Front Door · VPN Gateway / ExpressRoute · Azure Backup & Site Recovery · Storage Account (Blob / Files / Queue / Table)

Event-Driven Data Pipeline

High-volume ingestion through Event Hubs, landed in Storage as a data lake, with Azure SQL serving the curated layer.

Event Hubs · Storage Account (Blob / Files / Queue / Table) · Azure SQL Database · Key Vault

Serverless API Backend

Azure Functions behind API Management as the public gateway, backed by PostgreSQL Flexible Server, with Managed Disks resiliency behind whatever VM-based tooling supports the pipeline.

Azure Functions · API Management · Azure Database for PostgreSQL Flexible Server · Managed Disks · Key Vault