As we said in a previous post, AWS Well Architected Framework was launched officially in 2015. The Microsoft Azure WAF approach took more time as they started later, about 2020 with their own WAF methodology. Anyway it´s a collection of best practices, guides and blue prints in the same way that their competitors, Google (in this case, they called it “4 key architecture principles/pillars”, but covers the similar points), and AWS based in experiences and feedback from several stakeholders.
To Summarize, Azure or AWS WAF or the 4 Key Google architecture principles/pillars, helps cloud architects to build secure, high-performing, resilient, and efficient infrastructure for their applications and workloads for their business. Moreover, provide a better UX (user experience) for the employees and users.
From the Microsoft point of view, there are also 5 clear pillars as well as for AWS:
- Cost Optimization – Focus on managing costs and reduce it as much as possible according with the scenario
- Operational Excellence –Focus on achieving excellence on operations processes that keep a system running in production.
- Performance Efficiency – Focus on achieving the best adoption of an IT solution in the cloud.
- Reliability – Focus on recovering a system or IT solution from failures and continue to function in the cloud.
- Security – Protecting applications and data from threats, keeping in mind the shared responsibility where a customer and Microsoft or some partners work together for a giving IT solution.
Did you notice any change comparing to AWS below?. Well, Microsoft wants to pointed out the same pillars but involve some extra staff around the pillars to make more powerful their offering. That means: references architectures, Azure Advisor as a point to start as well as CCO Dashboard, Cloudockit, AZGovViz, specific partners offerings or the WAF Review reporting (this is not different from AWS).
The Azure approach for the Well Architected Framework provides some changes in the steps to go ahead comparing to AWS. They are more HLD (high level design) to drill down later while Microsoft try to gather more details in order to sort out priorities, responsibilities and tools to address the right technologies to the right issues sooner.
It seems that this workshop process will be run smoothly and easy to use. The truth is, you will get struggle with some Workloads or specific IT components for sure. But what are the most important Microsoft Azure architecture “Quality Inhibitors” to face with?
Cost Optimization –
Operational Excellence –
Performance Efficiency –
Underused or orphaned resources
No automation or Silos automation
No design for scaling
No support for disaster recovery
No security threat
As you can see, each hyperscaler has its own vision. But they are similar in the areas to evaluate and to fix when something is not working properly.
In the next post, we will cover more in depth similarities and differences between the two big cloud titans, Azure and AWS. In the meanwhile, the ball is in your court. Read, read and read…for sure you do… 🙂
Enjoy the journey to the cloud with me…see you then in the next post.