Well-Architected Review: Why, What and How
Summary
Reviewing regularly is important for continual improvement, for revisiting tradeoffs and design decisions, and because application requirements and available cloud features change over time. The well-architected framework was introduced by AWS in 2012 (published publicly in 2015) to share the experience of solution architects building systems across many business verticals and use cases. These questions are from the well-architected framework whitepapers, and the tool includes links to useful background material, and some advice for how to apply this for an application running in AWS. Importantly, there is a scoring mechanism that marks questions as high and medium risk based on AWS’ analysis of many thousands of workloads. It is more efficient to talk to cloud experts who can navigate the many options available: to make recommendations, answer your specific questions, and ensure the solution is right for your context.