Application SLA

Azure customers can use SLAs to evaluate how their Azure solutions meet their business requirements and the needs of their clients and users.
By creating your own SLAs, you can set performance targets to suit your specific Azure application.
When creating an Application SLA consider the following:
- Identify workloads - Each workload has different requirements for availability, scalability, data consistency, and disaster recovery.
- Plan for usage patterns - Identify differences in requirements during critical and non-critical periods.
- Establish availability metrics.
- Establish recovery metrics.
- Implement resiliency strategies.
- Build availability requirements into your design - Availability is the proportion of time your system is functional and working.
If your application SLA defines four 9's (99.99%) performance targets, recovering from failures by manual intervention may not be enough to fulfil your SLA. Your Azure solution must be self-diagnosing and self-healing instead. It is difficult to respond to failures quickly enough to meet SLA performance targets above four 9's.

Last updated 4 years ago

Was this helpful?

Azure customers can use SLAs to evaluate how their Azure solutions meet their business requirements and the needs of their clients and users.
By creating your own SLAs, you can set performance targets to suit your specific Azure application.
When creating an Application SLA consider the following:
- Identify workloads - Each workload has different requirements for availability, scalability, data consistency, and disaster recovery.
- Plan for usage patterns - Identify differences in requirements during critical and non-critical periods.
- Establish availability metrics.
- Establish recovery metrics.
- Implement resiliency strategies.
- Build availability requirements into your design - Availability is the proportion of time your system is functional and working.
If your application SLA defines four 9's (99.99%) performance targets, recovering from failures by manual intervention may not be enough to fulfil your SLA. Your Azure solution must be self-diagnosing and self-healing instead. It is difficult to respond to failures quickly enough to meet SLA performance targets above four 9's.

Last updated 4 years ago

Was this helpful?