Book Image

Optimizing Microsoft Azure Workloads

By : Rithin Skaria
Book Image

Optimizing Microsoft Azure Workloads

By: Rithin Skaria

Overview of this book

It’s easy to learn and deploy resources in Microsoft Azure, without worrying about resource optimization. However, for production or mission critical workloads, it’s crucial that you follow best practices for resource deployment to attain security, reliability, operational excellence and performance. Apart from these aspects, you need to account for cost considerations, as it’s the leading reason for almost every organization’s cloud transformation. In this book, you’ll learn to leverage Microsoft Well-Architected Framework to optimize your workloads in Azure. This Framework is a set of recommended practices developed by Microsoft based on five aligned pillars; cost optimization, performance, reliability, operational excellence, and security. You’ll explore each of these pillars and discover how to perform an assessment to determine the quality of your existing workloads. Through the book, you’ll uncover different design patterns and procedures related to each of the Well-Architected Framework pillars. By the end of this book, you’ll be well-equipped to collect and assess data from an Azure environment and perform the necessary upturn of your Azure workloads.
Table of Contents (14 chapters)
1
Part 1: Well-Architected Framework Fundamentals
4
Part 2: Exploring the Well-Architected Framework Pillars and Their Principles
10
Part 3: Assessment and Recommendations

Building Reliable Applications

In the previous chapter, we covered performance efficiency where we saw how we can make sure that our application withstands sudden demand. Now, we will start covering another pillar of the WAF – that is, reliability. Organizations offer service-level agreements (SLAs) and service-level objectives (SLOs) to their end users. Applications should meet these commitments, and with reliability, we are ensuring that these commitments are met. By incorporating reliability into our architecture, we make sure that our workloads are available and can recover from catastrophic failures regardless of the scale of the failure. Compared to the previous chapter, this chapter will be short as we have covered most of the testing and monitoring solutions before.