Reliability and Performance
Keeping systems fast and standing when parts fail: common performance antipatterns, timeouts and retries, circuit breakers, bulkheads, health checks, throttling and compensation.
- 7 topics
- Quiz on every topic
0% read
- 0 / 7topics read
- –average quiz score
- 0 daysreading streak
- 0saved to revise
Your progress is saved in this browser. Nothing is sent to us.
Module 10
Reliability and Performance
-
10.1
Read
Performance Antipatterns
Most slow systems are slow for the same few reasons. A tour of ten common performance antipatterns, from the busy database and chatty I/O to retry storms and noisy neighbours, with how to spot and fix each one.
-
10.2
Read
Timeouts, Retries, Backoff and Jitter
Every remote call can hang or fail. Learn how to set timeouts, when retrying helps and when it hurts, and why exponential backoff with jitter is the standard way to retry without causing a retry storm.
-
10.3
Read
Circuit Breaker
A circuit breaker stops calling a dependency that keeps failing, so your service fails fast instead of waiting on timeouts, and the dependency gets room to recover. Learn the closed, open and half-open states and how to tune them.
-
10.4
Read
Bulkhead
A ship's bulkheads keep one flooded compartment from sinking the ship. In software, separate pools of threads, connections or servers keep one failing dependency or noisy tenant from taking everything down.
-
10.5
Read
Health Checks and Health Endpoints
Load balancers, orchestrators and monitoring all need to know whether an instance can do its job. Learn liveness vs readiness checks, what a health endpoint should test, and how health checks can cause outages.
-
10.6
Read
Throttling and Queue-Based Load Leveling
Traffic is spiky, but capacity is not. Throttling caps how much work each client or the whole system accepts; queue-based load leveling turns bursts into a steady stream. Learn when to use each and how they fit with autoscaling.
-
10.7
Read
Compensating Transactions
When a multi-step operation fails halfway and the finished steps cannot be rolled back, you undo them with new actions: refunds, cancellations, corrections. Learn how to design compensations that are safe to retry and honest about what cannot be undone.