Reliability for Backend Developers
Reliability is keeping a backend working when parts fail or load grows. Resilience patterns such as timeouts, retries with backoff, circuit breakers and bulkheads contain failures, while scaling approaches such as horizontal scaling, load balancing, read replicas and sharding handle more traffic.
Stage: Architecture and Scale · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Reliability
- Add timeouts and exponential backoff with jitter to outbound calls
- Explain how a circuit breaker prevents cascading failure
- Scale a stateless service horizontally behind a load balancer
- Use read replicas and sharding to scale a database
- Define availability targets using SLOs
Reliability interview questions
Why add jitter to retries?
If many clients retry on the same schedule after an outage, their retries arrive together and can overload the recovering service again. Adding random jitter to the backoff delay spreads retries over time and prevents these synchronised spikes.
Why does horizontal scaling improve reliability more than vertical scaling?
Vertical scaling gives one machine more CPU or memory, which is simple but has a ceiling and a single point of failure. Horizontal scaling adds more machines behind a load balancer, which needs stateless services or shared state but scales further and tolerates failures.
Where Reliability fits in the Backend Developer roadmap
Reliability belongs to the Architecture and Scale stage (beginner level), which takes about 5 hours. Make services reliable under load.
Other units in this stage
Back to the full Backend Developer roadmap