---
schema_version: "1"
id: 6510689be398aeff7a44443504a07100cc0d1a9067843daa0797d07d8a6302f5
title: Reliability — Patterns
collection: architect
version: next
locale: en-us
portal_url: https://docs.salesforce.com/architect/next/en-us/well-architected/guides/reliability-overview.md
canonical_url: https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability-overview.html
source_site: staging.architect.salesforce.com
content_type: documentation
content_hash: e999f5685c9fa6c416b828dabe543aa4e2271dfe981e9d6c6c3a46f281c4f861
products:
  - Well-Architected Framework
  - Architect Site Content Repo
---
# Reliability — Patterns

The Reliability pillar focuses on system availability, performance, disaster recovery, and scalability, so your solutions withstand failures and scale with demand. These patterns turn the pillar's design principles into concrete, reviewable practices: what to look for in a solution, what good looks like, and the anti-patterns that undermine it.

## Design Principles

These patterns put the Reliability pillar's design principles into practice. Read them alongside the [Reliability pillar](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability.md) for the full guidance behind each one.

- **Distribute workload through bulkification** — process in batches so a spike in volume doesn't exhaust governor limits.
- **Assume everything fails** — design for the failure of every dependency, not just the ones you expect.
- **Build self-recovering systems** — recover automatically from transient failures rather than requiring manual intervention.
- **Design for business requirements first** — ground availability and recovery targets in business impact, not arbitrary uptime figures.
- **Validate recovery through drills** — prove your disaster-recovery procedures work before you need them.

## How to Use These Patterns

Each category pairs **patterns** (what good looks like) with **anti-patterns** (what to avoid), organized so you can review a solution area by area. Start from the reliability outcome you need:

- **Setting or defending availability and latency targets?** Begin with **Availability and Performance** to ground SLOs in business impact before choosing an architecture.
- **Protecting against data loss or regional failure?** Use **Disaster Recovery** to align backup, failover, and business-continuity procedures to your RPO/RTO.
- **Handling growth or spiky load?** Use **Scalability** to bulkify workloads and stay within governor limits as volume rises.
- **Operating agents in production?** Use **Agentic Patterns** for fallback chains, timeout handling, and agent health monitoring.

## Pattern Categories

### [Agentic Patterns](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability-agentic-patterns.md)
Reliability-specific patterns for agentic systems including fallback strategies, timeout handling, and agent health monitoring.

### [Availability and Performance](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability-availability-performance-patterns.md)
Patterns for high availability, performance optimization, caching, and load management.

### [Disaster Recovery](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability-disaster-recovery-patterns.md)
Patterns for backup strategies, data recovery, business continuity, and failover procedures.

### [Scalability](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability-scalability-patterns.md)
Patterns for horizontal and vertical scaling, governor limit management, and handling growth.

## Related Resources

- [Reliability pillar](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/reliability.md) — the design principles and architectural guidance these patterns implement
- [Reliability for the Agentic Enterprise](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/agentic-enterprise-reliability.md) — reliability guidance for agent-based solutions
- [Well-Architected Framework](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/framework.md) — how Reliability fits alongside the other pillars
- [Patterns and Anti-Patterns](https://staging.architect.salesforce.com/docs/architect/well-architected/guide/patterns-and-anti-patterns.md) — the full pattern library across all pillars