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 84. Handling Network Failures in the Cloud

Shayon Mukherjee

In the era of cloud computing, network failures—especially transient ones—are a given. These failures come in many forms and can originate from servers, routers, load balancers, connection pools, software applications, human errors, and, of course, the DNS. Writing software applications for the cloud in a distributed system environment therefore requires an added degree of care and a resiliency mindset. Use this mindset to incorporate practices during software development that will allow your applications to withstand these failures without disrupting customer experiences.

A common way to handle network failures is through the use of timeouts, retries, and retries with backoff and jitter. As a cloud engineer, it should become part of your DNA to enforce these practices when dealing with network connectivity or similar communication protocols over the internet—because things always go wrong in production.

A timeout, in simple terms, refers to the maximum time allowed for a connection to sit idle. Lack of time-outs when combined with connectivity issues to another service often leads to increased latency and resource exhaustion. In such a scenario, a client and server are waiting on a request that may never complete, resulting in a nonoptimal customer experience. As a cloud engineer, ...

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