AzureArchitectureBook_StudyCards Flashcards
Topics 1.1.
‘1)Learning about Azure’s global footprints, 2) Understanding the design of cloud-scale data centers, 3) Design for cloud
MCIO = GFS
The team that manages and runs Azure infrastructure is called Microsoft Cloud Infrastructure and Operations (MCIO), formerly known as Global Foundation Service (GFS). Also Microsoft datacenters = Azure Datacenters
Azure global footprints
‘+1 M servers, +3M requests per second. 17 datacenters distributed, 10 languages, 19 currencies
17 Regions
‘1) USA 8, Emea 2, Asia 2, Japan 2, Brazil 1, Australia 2
ZRS
Zone Redundant Storage, 3 copies of your data across 2 or 3 facilities in a single region or two regions
Affinity Group
It is a way to group your cloud sevices by proximity to reduce network latency.
STAMPS
Group of server racks (it’s not an official concept)
Regional Differences
Not all Azure regions provide the same set of services.
Multilanguage support
It’s not tied to specific regions. Full globaly. By aware! many Azure objects don’t allow non-English characters in their names or identifi ers.
Cloud-scale datacenters
A single Azure datacenter can be as big as three large cruise ships placed end to end and host ten of thousands of servers.
Embracing errors
Cloud-scale datacenters use commodity servers to reduce cost. The availability of these servers are low than more expensive ones used in traditional datacenters. Think about thousands! Traditional datacenters design focus on increasing Mean Time Between Failures (MTBF). In Cloud-scale datacenters when a server is failing its workloads are redirected to another healty one. So the design key is focus on Mean Time To Recover (MTTR) instead of MTBF because what customer cares is about the availability of their services, not the hardware. To achieve this AUTOMATIZATION IS THE KEY.
