Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 3, Azure Arichitecture - Coggle Diagram
Chapter 3
Azure Arichitecture
:one:
Regions & Availability Zones
:star:
Region Definition
:star:
A region is a set of data centers deployed within a latency defined perimeter and connected thought a dedicated regional low latency network
:star:
Broken Down
:green_cross:
A set of data centers
Each region has more than one data center which is a physical location
:green_cross:
Latency defined perimeter
Latency is the time it takes data travel. Also means that data centers are not "too far" from each other
:green_cross:
"Regional low-latency network"
A fiber connection between data centers in the region
:star:
How to choose a Region
:green_cross:
Location
Choose a region closest to your users to minimize latency
:green_cross:
Features
Some features aren't all regions. If you need a specific feature, some regions might be unavailable
:check:
Price
The price of services vary from region to region
:fire:
Paired Region
:check:
Each region is paired
Paired within same geo graphic area except Brazil South
:check:
Outage Failover
If the primary region has an outage you can failover to the secondary region
:check:
Planned Updates
Only one region in a pair is updated at any one time
:star:
Availability Zones
:check:
Physical Location
Each availability zone is a physical location within a region
:check:
Independent
Each zone has its own power, cooling and networking
Zones
Each region has a minimum of three zones
:checkered_flag:
Summary
:sa:
Azure Region
A set of data centers that are close enough to each other that it doesn't matter which data center your data is in. Latency is the time it takes for data to travel
:warning:
Availability Zone
Within a region and each zone has its own separate power, cooling and networking. Used for protecting data from failures.
:two:
Resource Groups & Azure Resource Manager
:star:
Resource Groups
:pencil2:
Think of it as a container that holds related resources
:pen:
Resource Group Facts
:check:
One Resource
Each resource can only exist in a single resource group
:check:
Add/Remove
You can add or remove resources to any resource group a any time
:check:
Move Resource
You can move a resource from one resource group to another
:check:
Multiple Regions
Resources from multiple regions can be in one resources group
:check:
Access Control
You can give users access to a resource group and everything in it
:check:
Interact
Resources can interact with other resources in different resource groups
:check:
Location
A resource group has a location, or region, as it stores meta data about the resources in it
:black_flag:
Azure Resource Manager (ARM)
is the underpinning of everything on Azure when it comes to creating, updating, or deleting resources. It is deployment and management services for Azure
:star:
ARM Benefits
:check:
1 more item...
:check:
1 more item...
:check:
1 more item...
:check:
1 more item...
:beer_mugs:
1 more item...
:check:
1 more item...
:pencil2:
Summary
:check:
Resource Groups
All resources belong to a resource group. It isn't a resource, but helps structure your Azure architecture
:check:
Azure Resource Manager
All interaction whit Azure resources go through the ARM. It is the main Azure Architecture component for creating, updating and manipulating resources