Book Image

Implementing Azure Solutions - Second Edition

By : Florian Klaffenbach, Markus Klein, Sebastian Hoppe, Oliver Michalski, Jan-Henrik Damaschke
Book Image

Implementing Azure Solutions - Second Edition

By: Florian Klaffenbach, Markus Klein, Sebastian Hoppe, Oliver Michalski, Jan-Henrik Damaschke

Overview of this book

<p>Microsoft Azure offers numerous solutions that can shape the future of any business. However, the major challenge that architects and administrators face lies in implementing these solutions. </p><p>Implementing Azure Solutions helps you overcome this challenge by enabling you to implement Azure Solutions effectively. The book begins by guiding you in choosing the backend structure for your solutions. You will then work with the Azure toolkit and learn how to use Azure Managed Apps to share your solutions with the Azure service catalog. The book then focuses on various implementation techniques and best practices such as implementing Azure Cloud Services by configuring, deploying, and managing cloud services. As you progress through the chapters, you’ll learn how to work with Azure-managed Kubernetes and Azure Container Services. </p><p>By the end of the book, you will be able to build robust cloud solutions on Azure.</p>
Table of Contents (14 chapters)

LoadBalancerProbes

The Azure Load Balancer (ALB) is responsible for routing incoming traffic to your role instances. In order for the traffic to be correctly routed, ALB must first send a query to the respective endpoints and check that the URI returns a HTTP 200 OK code. This process is called load balancer probe.

In other words, the load balancer probe is a customer defined health probe of endpoints in your role instances.

A LoadBalancerProbes is not a standalone element, but exists in combination with a WebRole or a WorkerRole. A LoadBalancerProbes may be provided for more than one role.

A template of a LoadBalancerProbes element looks like this:

<ServiceDefinition ...> 
<LoadBalancerProbes>
<LoadBalancerProbe name="<load-balancer-probe-name>"
protocol="[http | tcp]"
path="<uri-for-checking-health-status-of-vm>"
port="<port-number>" intervalInSeconds="<interval-in-seconds>...