Performance Efficiency – The system’s ability to adapt to changes in load. Operational Excellence – Operational processes which keep a system operating in production.Cost Optimisation – Managing costs to increase the value produced.This framework is based on five pillars of architectural best practices for Azure workloads: The Microsoft Azure Well-Architected Framework is a set of guiding principles to improve the overall quality of a workload. FIVE PILLARS OF THE AZURE WELL-ARCHITECTED FRAMEWORK In either case, adopting a Well-Architected Framework is equally important. While this approach can certainly be taken to review and improve existing applications and workloads already in the cloud, it is easier to plan for a Well-Architected Framework during the initial deployment stages than it is to re-design once you are already there. Part one of this blog introduces the five pillars of the Microsoft Azure Well-Architected Framework using some common scenarios we see and questions we receive from customers. When working with Partners and their customers we use the Well-Architected Framework to check how an application/workload measures up to Microsoft’s best practices for Azure. I wanted to answer a common question I know a lot of people ask “what’s the difference between the Well-Architected Framework and the Cloud Adoption Framework for Azure”?Īzure’s Well-Architected Framework targets a specific workload and the Cloud Adoption Framework picks them up from the point of migration to the cloud. In this blog series we take a deep dive into the five pillars of the Microsoft Azure Well-Architected Framework (WAF) and highlight some of the most useful aspects.
0 Comments
Leave a Reply. |