Skip to content

Commit 34c8deb

Browse files
committed
Remove reference to old image
1 parent f42cd1f commit 34c8deb

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/reliability/overview.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,6 @@ The required level of reliability for any Azure solution depends on several cons
3232

3333
Building reliability systems on Azure is a **shared responsibility**. Microsoft is responsible for the reliability of the cloud platform, including its global network and data centers. Azure customers and partners are responsible for the resilience of their cloud applications, using architectural best practices based on the requirements of each workload. While Azure continually strives for highest possible resiliency in SLA for the cloud platform, you must define your own target SLAs for each workload in your solution. An SLA makes it possible to evaluate whether the architecture meets the business requirements. As you strive for higher percentages of SLA guaranteed uptime, the cost and complexity to achieve that level of availability grows. An uptime of 99.99 percent translates to about five minutes of total downtime per month. Is it worth the more complexity and cost to reach that percentage? The answer depends on the individual business requirements. While deciding final SLA commitments, understand Microsoft’s supported SLAs. Each Azure service has its own SLA.
3434

35-
:::image type="content" source="media/shared-responsibility.svg" alt-text="Diagram showing the shared responsibility model for Azure business continuity.":::
36-
3735
In the traditional on-premises model, the entire responsibility of managing, from the hardware for compute, storage and networking to the application, falls on you. You must plan for various types of failures and how to deal with them by creating a [business continuity strategy](./concept-business-continuity-high-availability-disaster-recovery.md). With IaaS, the cloud service provider is responsible for the core infrastructure resiliency, including storage, networking, and compute. As you move from IaaS to PaaS and then to SaaS, you’ll find that you’re responsible for less and the cloud service provider is responsible for more.  
3836

3937
For more information on Reliability principles, see [Well-architected Framework Reliability documentation](/azure/well-architected/resiliency/).  

0 commit comments

Comments
 (0)