Please enable JavaScript.
Coggle requires JavaScript to display documents.
Module 2 - Architectural Components (Architectural Components (Resource…
Module 2 - Architectural Components
Architectural Components
Geographies - Europe, Americas etc
a discrete market containing 2 or more regions that preserves data residency and compliance boundaries
ensure
data residency, sovereignty, compliance and resiliency requirements are honored
Region Pairs
- each region is paired with another in the same geography
Region Recovery Order
in the event of a broad outage, recovery of
one region is prioritized out of the pair
Sequential Updates
systems update are rolled out to paired regions sequentially to
minimize downtime, the effect of bugs and logical failures
Platform-provided Replication
some services such as geo-redundant storage provide
automatic replication to the parallel region
Data Residency
region reside within the same geography as its pair to meet data residency requirements for tax and law enforcement jurisdiction purposes
Physical Isolation
Azure prefers at least
300 miles of separation
between DCs in a RP - natural disasters, power outages, physical network outages
Availability Sets
a way for you to
ensure your app remains online
if a high-impact maintenance event is required, or a HW failure occurs
Update Domain
when a maintenance event occurs, the
update is sequenced through update domains
logical section of the DC,
implemented with software and logic
this ensures that the entire DC isn't available during platform updates and patching
Fault Domain
provide for the
physical separation of your workload across different HW
in the DC
includes
power, cooling, and network HW that supports the physical servers
Regions
Provide customers the
flexibility and scale
needed to bring apps closer to their users
Preserve data residency
and offer
comprehensive compliance & resiliency options
geographical area on the planet, with multiple datacenters in close proximity that are networked together in a
low-latency network
- eg. West Europe
Some services or VM features are only available in certain regions -
VM sizes, storage types
Availability Zones
allow users to run mission-critical apps with
high availability and low-latency-replication
Each AZ is an
isolation boundary
containing one or more DCs equipped with
independent power, cooling and networking
physically separate locations within an Azure Region that use availability sets to provide additional
fault tolerance
Resiliency
- minimum of 3 separate zones in all enabled regions
Resource Groups
when you delete a RG you delete all the resources contained in it
Metering & Billing, Policies, Monitoring & Alerts, Quotas, Access Control
each resource must exist in one, and only one RG
unit of management for resources in Azure
. Container that allows you to aggregate and mange all the resources required for your app in a single unit
A RG can contain resources that reside in different regions
resources for an app do not need to exist in the same RG, but it is recommended
Resource Manager
Deploy Application Resources
- update, manage & delete all the resources for your solution in a single co-ordinated operation
Organize Resources
- manage your infrastructure through declarative templates rather than scripts. View which resources are linked by a dependancy and apply tags to categorize them for task such as billing
Control Acccess & Resources
- you control who can perform actions on the resources. You manage permissions by defining roles, adding users or groups to the roles and applying policies at RG level
allows you to automate the deployment and configuration of resources - Azure Powershell, Azure CLI, Azure Portal, REST API, Client SDKs