The AWS Well-Architected Framework is based on five pillars — operationalexcellence, security, reliability, performance efficiency, and cost optimization.
In AWS Well-Architected Framework, we also may use the following terms:
- Component is the code, configuration and AWS resources that together deliver against a requirement. A component is often the unit of technical ownership, and is decoupled from other components
- Workload to identify a set of components that together deliver business values. The workload is usually the level of detail that business and technology leaders communicate about.
- Milestones mark key changes in your architect as it evolves thru the product lifecycle (design, teseting, go live, and in production)
- Architect how components work together in a workload. How components communicate and interact is often the focus of architecture diagrams
- Technology Portfolio is the collection of workloads that are required for the business to operate.
When architecting workloads you make trade-offs between pillars based on your business context. For example:
- You might reduce cost at the expense of reliability in dev environment.
- For mission critical solutions, you might optimize reliability with increased costs.
- In ecommerce solutions, performance can effect revenue and customer propensity to buy.
Security and Operational excellence are generally not trade-off against the other pillars.