It also aids in the resolution of those instances through social media.

Windows Azure's Fabric Controller is a key component of the platform's architecture. When we consider the components and services supplied by Windows Azure, we wonder how it all works and what is going on in the clouds. From our perspective, it appears to be somewhat complicated. To have a better grasp of the Fabric Controller, let's look at the actual architecture of these services.

Many devices or servers are aggregated via a switch inside the data center. Fabric controller may be thought of as the brain of the Azure service, analyzing operations and making choices. A switch aggregates a set of machines in Microsoft's data center to form a fabric. Cluster refers to a collection of these devices. A fabric controller manages and owns each cluster. Along with these devices, they are reproduced. It controls everything within those computers, including load balancers, switches, [url="https://www.igmguru.com/cloud-computing/microsoft-azure-solution-architect-az-300-training/"]azure training[/url], and other components. A fabric agent is installed in each machine, and the fabric controller may communicate with each fabric agent.

Fabric controller performs operating system, patch updates, and software upgrades when a user selects one of the virtual machines. One of the Fabric Controller's most significant duties is to determine where the new application should execute. It also chooses the physical server to get the most out of the hardware.

When a new application is published on Azure, it comes with an XML application configuration file. The fabric controller reads such files in the Microsoft data center and makes the appropriate adjustments.

It not only manages resource allocation to a given application, but it also keeps track of the health of compute and storage services. It also allows a system to recover from failures.

Consider the following scenario: There are four instances of web role running, and one of them dies. The fabric controller will instantly start a new instance to replace the one that has died. Similarly, if any virtual machine fails, the fabric controller assigns a new one. After allocating the new machine, it also resets the load balancers so that it points to the new machine immediately. In the Windows Azure architecture, the Fabric Controller is responsible for all intelligent tasks.