Skip to Content
97 Things Every Cloud Engineer Should Know
book

97 Things Every Cloud Engineer Should Know

by Emily Freeman, Nathen Harvey
December 2020
Beginner
308 pages
9h 5m
English
O'Reilly Media, Inc.
Content preview from 97 Things Every Cloud Engineer Should Know

Chapter 44. The Basics of Service-Level Objectives

Kit Merker, Brian Singer, and Alex Nauda

“I want it to work perfectly,” your boss or maybe a product manager tells you. But you, as a cloud engineer, know they aren’t really willing to pay for that level of service, even if it were possible, which it’s not.

How can you give management an easy way to instantly understand the trade-offs between reliability, speed of innovation, and cost? Service-level objectives (SLOs) are the answer. SLOs create clear reliability guidelines that balance the trade-offs between cloud costs, speed of change, and external risks.

What Are SLOs?

SLOs are key performance indicators for cloud services based on customer happiness. SLOs define the precise level of service that needs to be achieved in order to avoid unacceptable risk of displeasing the customer.

Let’s use availability as an example. When we talk about how often our infrastructure is available (uptime), we typically speak in terms of nines. If your infrastructure is available four nines, or 99.99%, it will be unavailable 52.6 minutes a year. However, if your infrastructure achieves five nines, then your system is up and working 99.999% ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

AirBnbBlueOriginElectronic ArtsHomeDepotNasdaqRakutenTata Consultancy Services

QuotationMarkO’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
Julian F.
Head of Cybersecurity
QuotationMarkI wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
Addison B.
Field Engineer
QuotationMarkI’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
Amir M.
Data Platform Tech Lead
QuotationMarkI'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Mark W.
Embedded Software Engineer

You might also like

97 Things Every Data Engineer Should Know

97 Things Every Data Engineer Should Know

Tobias Macey
97 Things Every SRE Should Know

97 Things Every SRE Should Know

Emil Stolarsky, Jaime Woo

Publisher Resources

ISBN: 9781492076728Errata Page