Architect Azure Environment - Availability and Recoverability

Designing for availability focuses on maintaining uptime through small-scale incidents and temporary conditions like partial network outages. You can ensure your application can handle localized failures by integrating high availability into each component of an application and eliminating single points of failure.

Such a design also minimizes the impact of infrastructure maintenance.

High-availability designs typically aim to eliminate the impact of incidents quickly and automatically and ensure that the system can continue to process requests with little to no impact.

e.g. VM's in side the Availability set and load balanced by the Load Balancer.



Designing for recoverability focuses on recovery from data loss and from larger scale disasters.

These types of incidents may result in some amount of downtime or permanently lost data. Disaster recovery is as much about careful planning as it is about execution.

For recoverability, perform an analysis that examines possible data loss and major downtime scenarios that includes RPO and RTO.

• Recovery Point Objective: The maximum duration of acceptable data loss. RPO is measured in units of time, not volume: "30 minutes of data", "four hours of data", and so on. RPO is about limiting and recovering from data loss, not data theft.
• Recovery Time Objective: The maximum duration of acceptable downtime, where "downtime" needs to be defined by your specification. For example, if the acceptable downtime duration is eight hours in the event of a disaster, then your RTO is eight hours.

With RPO and RTO defined, you can design backup, restore, replication, and recovery capabilities into your architecture to meet these objectives.


https://pachehra.blogspot.com/2019/06/architect-azure-environment-efficiency.html