Book Image

Azure Integration Guide for Business

By : Joshua Garverick, Jack Lee, Mélony Qin, Trevoir Williams
Book Image

Azure Integration Guide for Business

By: Joshua Garverick, Jack Lee, Mélony Qin, Trevoir Williams

Overview of this book

Azure Integration Guide for Business is essential for decision makers planning to transform their business with Microsoft Azure. The Microsoft Azure cloud platform can improve the availability, scalability, and cost-efficiency of any business. The guidance in this book will help decision makers gain valuable insights into proactively managing their applications and infrastructure. You'll learn to apply best practices in Azure Virtual Network and Azure Storage design, ensuring an efficient and secure cloud infrastructure. You'll also discover how to automate Azure through Infrastructure as Code (IaC) and leverage various Azure services to support OLTP applications. Next, you’ll explore how to implement Azure offerings for event-driven architectural solutions and serverless applications. Additionally, you’ll gain in-depth knowledge on how to develop an automated, secure, and scalable solutions. Core elements of the Azure ecosystem will be discussed in the final chapters of the book, such as big data solutions, cost governance, and best practices to help you optimize your business. By the end of this book, you’ll understand what a well-architected Azure solution looks like and how to lead your organization toward a tailored Azure solution that meets your business needs.
Table of Contents (15 chapters)

Understanding high availability with Azure

High availability refers to an important aspect of a service or application that ensures uninterrupted operations by meeting or surpassing its promised service-level agreement (SLA). Users are guaranteed a certain SLA based on the service type. For instance, an SLA might guarantee 99% availability for an application over the course of a year. This means the service should be accessible to users for a minimum of 361.35 days out of the 365-day period. Failure to meet this availability requirement would be considered a breach of the SLA.

In the case of mission-critical applications, the high-availability SLA is often up to 99.999% for the year. This means the application is expected to run continuously and remain accessible throughout the entire year, with a maximum allowable downtime of only 5.2 hours. If the actual downtime exceeds the defined SLA threshold, users may be eligible for credit, which is calculated based on the overall uptime...