Architecting For Scale by Lee Atchison
Author:Lee Atchison
Language: eng
Format: epub, pdf
Publisher: O'Reilly Media, Inc.
Published: 2016-07-24T16:00:00+00:00
What Is “Two Mistakes High”?
If you’ve ever flown radio control (R/C) airplanes before, you might have heard the expression “keep your plane two mistakes high.”
When you learn to fly R/C planes, especially when you began learning how to do acrobatics, you learn this quickly. You see, mistakes equate to altitude. You make a mistake, you lose altitude. You lose too much altitude, and well, badness happens. Keeping your plane “two mistakes high” means keeping it high enough that you have enough altitude to recover from two, independent mistakes.
Why two mistakes? Simple. You always want to be operating your plane high enough so that you can recover if (when) you make a mistake. Now, suppose that you make a mistake and lose a bunch of altitude. During your recovery from that mistake, you also want to be high enough that you can recover from a mistake. Think about it: during your recovery process, you are typically stressed and perhaps in an awkward situation doing potentially abnormal things—just the type of situation that can cause you to make another mistake. If you aren’t high enough, you can crash.
Put another way, if you normally fly two mistakes high, you can always have a backup plan for recovering from a mistake, even if you are currently recovering from a mistake.
This same philosophy is important to understand when building highly available, high-scale applications.
How do we “keep two mistakes high” in an application? For starters, when we identify the failure scenarios that we anticipate our application facing, we walk through the ramifications of those scenarios and our recovery plan for them. We make sure the recovery plan itself does not have mistakes or other shortcomings built into it—in short, we check that the recovery plan is able to work. If we find that it doesn’t work, then it’s not a recovery plan.
Download
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.
Disaster & Recovery | Email Administration |
Linux & UNIX Administration | Storage & Retrieval |
Windows Administration |
Sass and Compass in Action by Wynn Netherland Nathan Weizenbaum Chris Eppstein Brandon Mathis(7417)
Grails in Action by Glen Smith Peter Ledbrook(7313)
Kotlin in Action by Dmitry Jemerov(4662)
Management Strategies for the Cloud Revolution: How Cloud Computing Is Transforming Business and Why You Can't Afford to Be Left Behind by Charles Babcock(4141)
The Age of Surveillance Capitalism by Shoshana Zuboff(3437)
Learn Windows PowerShell in a Month of Lunches by Don Jones(3260)
Mastering Azure Security by Mustafa Toroman and Tom Janetscheck(3035)
Mastering Python for Networking and Security by José Manuel Ortega(2973)
Blockchain Basics by Daniel Drescher(2902)
Microsoft 365 Identity and Services Exam Guide MS-100 by Aaron Guilmette(2749)
TCP IP by Todd Lammle(2650)
Configuring Windows Server Hybrid Advanced Services Exam Ref AZ-801 by Chris Gill(2614)
Azure Containers Explained by Wesley Haakman & Richard Hooper(2501)
From CIA to APT: An Introduction to Cyber Security by Edward G. Amoroso & Matthew E. Amoroso(2490)
Hands-On Azure for Developers by Kamil Mrzyglod(2437)
React Native - Building Mobile Apps with JavaScript by Novick Vladimir(2346)
The Social Psychology of Inequality by Unknown(2323)
MCSA Windows Server 2016 Study Guide: Exam 70-740 by William Panek(2320)
The Art Of Deception by Kevin Mitnick(2308)