Policy: AWS > Well-Architected Tool > AWS Well-Architected Framework > Reliability > REL 05. How do you design interactions in a distributed system to mitigate or withstand failures?
Distributed systems rely on communications networks to interconnect components (such as servers or services). Your workload must operate reliably despite data loss or latency over these networks. Components of the distributed system must operate in a way that does not negatively impact other components or the workload. These best practices enable workloads to withstand stresses or failures, more quickly recover from them, and mitigate the impact of such impairments. The result is improved mean time to recovery (MTTR).
See REL 05. How do you design interactions in a distributed system to mitigate or withstand failures? for more information.
Targets
This policy targets the following resource types:
Primary Policy
This policy is used with the following primary policy:
Related Policies
- Set client timeouts
- Implement emergency levers
- Fail fast and limit queues
- Make services stateless where possible
- Implement graceful degradation to transform applicable hard dependencies into soft dependencies
- Control and limit retry calls
- Throttle requests
Controls
Setting this policy configures this control:
Policy Specification
Schema Type | |
|---|---|
Default | |
Valid Values [YAML] |
|
Examples [YAML] |
|
Category
In Your Workspace
Developers
- tmod:@turbot/turbot#/control/categories/other
- tmod:@turbot/aws-wellarchitected-framework#/policy/types/rel05
- turbot graphql policy-type --id "tmod:@turbot/aws-wellarchitected-framework#/policy/types/rel05"
- turbot graphql policy-settings --filter "policyTypeId:tmod:@turbot/aws-wellarchitected-framework#/policy/types/rel05"
Get Policy TypeGet Policy Settings