⭐ Repository → 💼 AWS Well-Architected → 💼 Reliability

💼 Workload architecture

• ID: /frameworks/aws-well-architected/reliability/workload-architecture

Description

A reliable workload starts with upfront design decisions for both software and infrastructure. Your architecture choices will impact your workload behavior across all six Well-Architected pillars. For reliability, there are specific patterns you must follow.

Similar

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Design interactions in a distributed system to mitigate or withstand failures	7				no data
💼 REL05-BP01 Implement graceful degradation to transform applicable hard dependencies into soft dependencies					no data
💼 REL05-BP02 Throttle requests					no data
💼 REL05-BP03 Control and limit retry calls					no data
💼 REL05-BP04 Fail fast and limit queues					no data
💼 REL05-BP05 Set client timeouts					no data
💼 REL05-BP06 Make systems stateless where possible					no data
💼 REL05-BP07 Implement emergency levers					no data
💼 Design interactions in a distributed system to prevent failures	4				no data
💼 REL04-BP01 Identify the kind of distributed systems you depend on					no data
💼 REL04-BP02 Implement loosely coupled dependencies					no data
💼 REL04-BP03 Do constant work					no data
💼 REL04-BP04 Make mutating operations idempotent					no data
💼 Design your workload service architecture	3				no data
💼 REL03-BP01 Choose how to segment your workload					no data
💼 REL03-BP02 Build services focused on specific business domains and functionality					no data
💼 REL03-BP03 Provide service contracts per API					no data