Do you use the Well-Architected Framework?

Last updated by Tiago Araújo [SSW] about 1 year ago.See history

The Well-Architected Framework is a set of best practices which form a repeatable process for designing solution architecture, to help identify potential issues and optimize workloads.

waf diagram revised
Figure: The Well-Architected Framework includes the five pillars of architectural excellence. Surrounding the Well-Architected Framework are six supporting elements

The 5 Pillars

Trade-offs

There are trade-offs to be made between these pillars. E.g. improving reliability by adding Azure regions and backup points will increase the cost.

Why use it?

Thinking about architecting workloads can be hard – you need to think about many different issues and trade-offs, with varying contexts between them. WAF gives you a consistent process for approaching this to make sure nothing gets missed and all the variables are considered.

Just like Agile, this is intended to be applied for continuous improvement throughout development and not just an initial step when starting a new project. It is less about architecting the perfect workload and more about maintaining a well-architected state and an understanding of optimizations that could be implemented.

What to do next?

Assess your workload against the 5 Pillars of WAF with the Microsoft Azure Well-Architected Review and add any recommendations from the assessment results to your backlog.

waf assessment
Figure: Some recommendations will be checked, others go to the backlog so the Product Owner can prioritize

waf reliability results 2
Figure: Recommended actions results show things to be improved

waf tech debt backlog northwind
Figure: Good example - WAF is very visible to the Product Owner on the backlog

We open source. Powered by GitHub