Reliability for Software Architects
Reliability is designing systems that keep working when parts fail. Resilience patterns such as timeouts, retries, circuit breakers and bulkheads limit damage, disaster recovery plans restore service within targets, and observability with SLOs measures whether users are getting the reliability promised.
Stage: Security, Reliability and Cost · Part of the Software Architect roadmap · Last reviewed 19 November 2026
What to learn in Reliability
- Add a circuit breaker and explain its closed, open and half-open states
- Use bulkheads to isolate failures between workloads
- Set recovery time and recovery point objectives for a system
- Compare backup, pilot light, warm standby and active-active
- Define an SLI, an SLO and an error budget
- Instrument a service with metrics, logs and traces
Reliability interview questions
What is an error budget?
An error budget is the amount of unreliability an SLO allows, such as 0.1 percent for a 99.9 percent target. While budget remains, teams can ship changes. When it is used up, work shifts to reliability until the service recovers.
What is the difference between RTO and RPO?
Recovery time objective is how long a system can be down before serious harm. Recovery point objective is how much data loss, measured as time since the last good copy, is acceptable. They drive the choice of backup and replication design.
Where Reliability fits in the Software Architect roadmap
Reliability belongs to the Security, Reliability and Cost stage (advanced level), which takes about 7 hours. The non-negotiables.
Other units in this stage
Back to the full Software Architect roadmap