Iqbal Sugandhi · Knowledge-sharing segment · 38 sessions
System Under Pressure
A learning series on large-scale systems for performance testing teams
From one user on one server to architectures that carry millions of transactions. Every component shows up as the answer to a problem you have already felt — not as a term to memorize.
0 / 38 sessions done
Every session done. You can now read a design doc like an insider.
Follow the video series @data_center_frog
No session matches.
Level 0 · Session 1–6
Reading the Pressure
What actually runs out when a system is “slow”?
Level 1 · Session 7–15
Multiplying Machines
If one server isn’t enough, what is the price of “many servers”?
- 07 The Server You Ordered, Not the One You Got
- 08 Bigger or More (Vertical vs Horizontal Scaling)
- 09 If There Are Two Servers, Who Decides? (Load Balancer & HAProxy)
- 10 Layer 4 and Layer 7: The Blind Guard vs the Smart Guard
- 11 One Door for Everyone: Reverse Proxy, Buffering, & Rate Limiting
- 12 Stateless Is a Requirement: Why Redis Is More Than a Cache
- 13 Every Server Is Up, the System Is Still Down: SPOF, High Availability, & Split Brain
- 14 When One Building Isn't Enough: GTM, Multi-DC, & Anycast DNS
- 15 The Robot That Keeps Pods Alive: Kubernetes, HPA, & Probes
Level 2 · Session 16–21
The Database Is the Bottleneck
Why does adding pods end up killing the system?
- 16 Pods Up, Database Down: The Arithmetic of Connection Storms & Lock Contention
- 17 The Database Gatekeeper: PgBouncer, ProxySQL, & Transaction Pooling
- 18 Reading Far More Often Than Writing: Read Replica & Replication Lag
- 19 Holding Questions Back from the Database: Redis Cache, Hit Ratio, & Thundering Herd
- 20 When One Database Isn't Enough: Sharding, Shard Keys, & Cross-Shard Queries
- 21 Separating the Read Path and the Write Path: CQRS & Materialized Views
Level 3 · Session 22–31
Systems That Depend on Each Other
How do hundreds of services fail together — and how do you prevent it?
- 22 When Services Are Split Apart: From Monolith to Microservices & the Danger of Fan-Out
- 23 The Languages Services Use to Talk
- 24 Traffic Between Services
- 25 The Domino Effect: Cascading Failure, Timeout, & Circuit Breaker
- 26 When Everyone Tries Again: Retry Storms, Jitter, & Backoff
- 27 Absorbing Load Without Waiting: Message Queue, Backpressure, & DLQ
- 28 Throttling the Flow: Rate Limiting, Leaky Bucket, & Token Bucket
- 29 Shooting Our Own Servers: Load Testing, Spike Testing, & Chaos Engineering
- 30 Seeing What Happens Inside: The Three Pillars of Observability (Logs, Metrics, & Traces)
- 31 Reading a Design Doc Like an Insider
Level 4 · Session 32–34
Eyes That Never Sleep
Who carries, stores, and shows the logs when an incident hits?
Level 5 · Session 35–38
Life and Death of a Pod on OpenShift
Where a pod is placed, when it counts as alive, how many connections it carries, and how it dies without errors?
- 35 The Probe That Kills Healthy Pods: Liveness, Readiness, & Startup Probes
- 36 The Last Seconds of a Pod: Graceful Shutdown, SIGTERM, & the preStop Hook
- 37 One Pod, 10 Connections; 200 Pods, 2,000 Connections: Redis Connection Pool Arithmetic
- 38 All Eggs in One Basket: topologySpreadConstraints, Anti-Affinity, & PodDisruptionBudget
How to use this series
- One session a week works well for a team with a day job.
- Don’t skip Level 0 — all of Level 2 rests on Sessions 3 and 6.
- Senior members can start at Session 16, but should still read Session 6.