Applications with internet facing needs effectiveness and maximum reliability with cloud native capabilities.
The architecture design targets an SLO of 99.999% uptime to a permitted annual downtime of 5 minutes and 13 seconds. To define a realistic uptime there are following promises we make to our users.
Service Level Agreements (SLA)
The agreement you make with your clients or users with yearly uptime commitments.
Service Level Objectives (SLO)
The objectives your team must hit to meet that agreement within an SLA about a specific metric like uptime or response time. SLOs are what set customer expectations and tell IT and DevOps teams what goals they need to hit and measure themselves against.
Service Level Indicator (SLI)
The real numbers on your performance measures compliance with an SLO. For example if your SLA is set that the platform will be available 99.999% of the time, your SLO is likely 99.99% uptime and your SLI is the actual measurement of your uptime of 99.95% or 99.9999%.
The Challenges of SLIs
As with SLOs the challenge of SLIs is keeping them simple, choosing the right metrics to track, and not overcomplicating IT’s job tracking too many metrics that don’t actually matter to clients.