⚡

ArchitectLab

Step 1 • v1.0

Multi-Cloud Principal Architect & FAANG System Design Workbench

Track 1 • Phase 1 • Topic 1.1

Vertical vs. Horizontal Scaling & Stateful vs. Stateless Servers

Experiment with incoming user traffic below. Watch what happens when you scale Vertically (Scale Up) on a single monster box versus Horizontally (Scale Out) across multiple commodity nodes—and toggle Session State to see why sticky local sessions break horizontal elasticity.

1. Architecture Controls

2,500 req/s
500 RPS (Quiet) 10,000 RPS (Viral) 20,000 RPS (Peak)
8 vCPU / 32 GB RAM
Tier 1 (Small) Tier 3 (Large) Tier 5 (Hardware Ceiling)

⚠️ Notice: Even Tier 5 hits a physical motherboard ceiling at 12,000 RPS and requires a reboot window to upgrade!

Server Session Architecture Where is user login/cart state stored?
Chaos Engineering: Test resilience by killing a primary server node.
System Status
● HEALTHY
Availability: 99.9%
CPU Utilization
42%
P99 Latency / Drop
28 ms
Dropped: 0%
Est. Cloud Cost
$320 / mo
Linear scaling
2. Live Topology Diagram Single-Node Vertical
🌍
Client Traffic
2,500 RPS
Direct DNS
No Load Balancer
🔒
Local RAM State

Sessions locked inside individual server memory.

Principal Architect Diagnostic:

Initializing diagnostic telemetry...