My Focus on astrology is how the planets are inducing its effects on people through gravity and light.,

What is Azure Well Architected Framework?

https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-2433481302961543 (adsbygoogle = window.adsbygoogle || []).push({});

To start this topic, we need to first understand what is Azure? A little deeper indeed!. In a nutshell, Azure is a Microsoft driven public cloud platform where 100’s of services are available for you to design your solution and to host your workloads. The big secret of “Well Architected Framework” is buried under the above single sentence actually. Azure Well Architect Framework (aka Azure WAF) is based on setting the guidelines to improve the quality of the solution and the environment. These guidelines are called frameworks, there are 5 pillars which define these guidelines to improve the quality. I am not going to start boring you by explaining the 5 pillars, I am leaving the choice for you to understand it. Microsoft has great documentation on those 5 pillars, so feel free to visit Microsoft

The Often misunderstood concept of WAF

When an architect is engaged for a WAF, the first thing he hears is one of the below (most of the times)

  • We need to deploy WAF 
  • The customer wants WAF when we can deploy it.
  • We are contractually obligated to deploy WAF 
  • Customer is very annoyed as we are not doing cost optimization so we need to deploy WAF
  • We need to deploy WAF in 2 week [most often 🙂 ]
To all those whose conversation has any of the above bullet points, let me tell you “Well Architected Framework” is not something that can be deployed, it’s a “Process” or “Framework” which helps you to fine tune your Azure environment and it takes time in establishing it.
How should WAF be used?

The most important thing to understand about WAF is, the process is little big and it will take months to bring in the changes in the customer environment. This is a recurring process which needs to be performed every 3 months or 6 months based on the customer or engagements. 

some of the use cases of WAF.

  • Cost optimization
  • Architecture best practice
  • Security best practices
  • Operation excellence
  • Reliability best practice.

Use the below simple continuous improvement process for WAF cycle to have great outcomes.

WAF Cycle

 

The above picture is self-explanatory for all techies so I am not going to explain those in detail. However, I will try to give you the real gist of WAF. As an architect, set the expectations clear about WAF in regards to what can be achieved, how much time it will take, who should be involved and what is the process. Ask for proper engagement as it would take a long time. Prepare the process document for the operations team or for the delivery team. “Take Ownership”, I am highlighting it since no one knows WAF better than you.

Thank you and feel free to share your comments…

 
 

More Posts

Leave a Reply