Book Image

Implementing Azure Cloud Design Patterns

By : Oliver Michalski, Stefano Demiliani
Book Image

Implementing Azure Cloud Design Patterns

By: Oliver Michalski, Stefano Demiliani

Overview of this book

A well designed cloud infrastructure covers factors such as consistency, maintenance, simplified administration and development, and reusability. Hence it is important to choose the right architectural pattern as it has a huge impact on the quality of cloud-hosted services. This book covers all Azure design patterns and functionalities to help you build your cloud infrastructure so it fits your system requirements. This book initially covers design patterns that are focused on factors such as availability and data management/monitoring. Then the focus shifts to complex design patterns such as multitasking, improving scalability, valet keys, and so on, with practical use cases. The book also supplies best practices to improve the security and performance of your cloud. By the end of this book, you will thoroughly be familiar with the different design and architectural patterns available with Windows Azure and capable of choosing the best pattern for your system.
Table of Contents (16 chapters)
Title Page
Packt Upsell

Service level objectives

In the last chapter, I tried to introduce you to the topic of service level agreement (SLA). An SLA is a contract that includes a guaranteed value for the availability. In addition to this guaranteed value, so-called service level objectives (SLOs) can also be used. But SLOs are not guarantees, but goals in the performance area. In other words, the service is just trying to reach a certain level. The entire environment and interaction with other services can have a negative impact.

Typical SLOs can be found in the following areas:

  • Throughput: How many operations can be performed in a given period of time?
  • Concurrency: How many operations can be performed simultaneously?
  • Latency: How long does the system take to perform an operation?
  • Headroom: How much capacity does the system have to allow growth?
  • Error rate: How many exceptions does the system generate while performing operations?


SLOs are also called Key Performance Indicators (KPIs).

Now we have learned a lot of theory...