Understanding Windows Azure Architecture: Hosts, Guests, Fabric Controller, and Fault Domains
Windows Azure, built on Hyper-V virtualization, organizes physical servers into Host and Guest virtual machines managed by a Fabric Controller that oversees multiple fault domains, using Host and Guest agents to monitor VM health and ensure reliable, on-demand cloud services.
Windows Azure, introduced in the 2012 preview, adds new virtual machine capabilities and an enhanced management portal, providing a PaaS operating system built on Hyper‑V virtualization for public‑cloud services.
Each physical server hosts a Windows Azure Host OS VM that manages multiple Windows Azure Guest OS VMs; the Host OS is responsible for controlling the underlying hardware while Guest OS VMs run customer workloads.
In a data‑center, groups of servers are organized into a management cluster called the Fabric Controller, which oversees multiple fault domains and coordinates the operation of all servers in the cluster.
Reliability is achieved by dividing the data‑center into fault domains; the Fabric Controller monitors each domain through a Windows Azure Host Agent installed on the Host OS, which reports VM status to the controller.
The Fabric Controller communicates with Host Agents, which in turn interact with Guest Agents on Guest VMs to collect version, service‑pack, configuration, and health information, enabling centralized monitoring and management of the Azure cloud.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Architects' Tech Alliance
Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.