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 6. A Cloud Computing Vocabulary

Jonathan Buck

In any profession, being able to speak and understand the vernacular goes a long way toward feeling comfortable in your role and working effectively with your colleagues. If you’re just starting your career as a cloud engineer, you will likely hear these terms throughout your workplace:

Availability
The amount of time  that a service is “live” and functional. This is often expressed in percentage terms. For example, if someone says their service has a yearly availability of 99.99%, that means it will be unavailable for only 52.56 minutes in an entire year.
Durability
Even for the most reliable devices, any data stored on a computer is ephemeral over a long enough time frame. Durability refers to the chance that data will be accidentally lost or corrupted over a given time period. Like availability, it’s typically expressed as a percentage value.
Consistency
Consistency refers to the notion that when you write data to a data store, it (or the latest version of it) might not be immediately available. This is because cloud-based data stores are built on distributed systems, and distributed systems are subject to the CAP theorem. (Also known as Brewer’s theorem, it holds that there are three things a distributed data store can guarantee—consistency, availability, and partition tolerance—but ...
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