And scales by cloning the app on multiple servers/VMs/Containers Traditional architecture approach Microservices architecture approach A microservice approach segregates functionality into separate services. And scales out by deploying independently and replicating these services across servers/VMs/containers A traditional application (web app or large service) usually has most of its functionality within a single process (Commonly internally layered, though). App 1 App 2 App 1

Microservices Azure Windows Server Linux Hosted Clouds Windows Server Linux Service Fabric Private Clouds Windows Server Linux High Availability Hyper-Scale Hybrid Operations High Density Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Load balancing Self-healing Data Partitioning Automated Rollback Health Monitoring Placement Constraints

Microservices Azure Windows Server Linux Hosted Clouds Windows Server Linux Service Fabric Private Clouds Windows Server Linux High Availability Hyper-Scale Hybrid Operations High Density Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Load balancing Self-healing Data Partitioning Automated Rollback Health Monitoring Placement Constraints

P S S S S Write Ack Read Value Write Ack

P S S S S S Must be safe in the presence of cascading failures B P Failed

Node 103 P S S Node 104 S S Node 102 P S S S Node 105 P S S S Node 101 S S P Node 100 S P S S P S S S

Microservices

Process