![]() ![]() The FC gets it’s marching orders from the “Red Dog Front End” (RDFE). An aggregator and load balancers manage groups of nodes, and all feed back to the Fabric Controller (FC), the operational heart of Azure. Each node - servers+top rack switch - is considered a ‘fault domain’, i.e., a possible point of failure. So how does Azure actually work:Īzure considers each rack a ‘node’ of compute power and puts a switch on top of it. What is great there is awesome explanation of Azure architecture and not in some big cubes in Visio that some architects draw with no details, but in terms of processes spawning more processes. Therefore I was really excited when someone pointed me to Kevin Williamson blog. Its against my nature to state that “something doesn’t work well and there is nothing we can do about it”, instead my favorite activity is to collect and pour through data and understand what is the cause – finding virtual “needle in the haystack”. Yet, that went completely against my idea that in order to develop well on something you have to understand its internals – after all I like to think of myself as sort of DevOps character, residing somewhere between development and infrastructure with good dose of DBA thrown in. So for a while all of us treated Azure PaaS as “black box development platform” and I am fairly sure in some ways it was intended to be so when introduced. They both moved me to do something to understand this topic deeper and huge thanks to both for information they shared with me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |