MugUp logoMugUp
HomeBrowseAboutBlog
LoginSign Up
MugUp

Plan your day, study, read, write and track your habits in one app.

Follow MugUp

Product

  • Features
  • Compare
  • Free Tools
  • Deck Library
  • MugUp for Discord

Community

  • Blog
  • Changelog
  • Feature Requests
  • Deck Requests

Company

  • Home
  • About
  • Contact

© 2026 MugUp. All rights reserved.

Terms of ServicePrivacy PolicyCookie Policy
  1. Browse decks
  2. Site Reliability Engineering (SRE)
Public deck

Site Reliability Engineering (SRE)

How to run production systems reliably, as Google's SRE books and common industry practice describe it: reliability targets and error budgets, alerting, incident response, postmortems, capacity, resilience patterns and chaos testing.

Engineering
AShared by Alex Chen
0PlaySign in to clone

You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.

See the whole deck

Suggested order

Arrows point from what to learn first. Topics side by side can be studied in any order — and cloning the deck brings this order with it.

Topics

Open a topic to read through its content, then play just that topic.

SRE Principles: Toil, Automation and the Error Budget
What SRE is, what counts as toil and why it is capped, and how an error budget turns a reliability target into a rule for when to ship.
MCQ: 10
Fill-in: 8
Flashcards: 11
Pair match: 10
39 total questions
SLIs, SLOs and SLAs in Practice
How to choose what to measure, set a target for it, write a contract around it, and work out how much downtime each level of availability allows.
MCQ: 10
Fill-in: 8
Flashcards: 11
Pair match: 10
39 total questions
Monitoring and Alerting Design
What to measure, which conditions should page a person, and how burn-rate alerts on an SLO catch both fast and slow problems without flooding the on-call engineer.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
Incident Response and On-Call
How a team runs an incident from the first page to the all-clear: severity levels, who does what, stopping the damage before finding the cause, and keeping on-call sustainable.
MCQ: 10
Fill-in: 8
Flashcards: 10
Pair match: 10
Locked · 38 questions inside
Postmortems and Learning from Incidents
How to write a blameless postmortem, why one root cause is rarely the whole story, and how to turn what you learn into action items that actually get done.
MCQ: 10
Fill-in: 8
Flashcards: 10
Pair match: 10
Locked · 38 questions inside
Capacity Planning and Load Testing
How to forecast the capacity a service needs, how much spare to keep for failures, and how to test that it holds up under load.
MCQ: 10
Fill-in: 8
Flashcards: 10
Pair match: 10
Locked · 38 questions inside
Resilience Patterns: Timeouts, Retries, Circuit Breakers and Bulkheads
How services survive slow or failing dependencies: timeouts and deadlines, retries with backoff and jitter, circuit breakers, bulkheads and serving a reduced page when parts are down.
MCQ: 10
Fill-in: 8
Flashcards: 12
Pair match: 10
Locked · 40 questions inside
Chaos Engineering and Disaster Testing
How teams find weaknesses on purpose by injecting failures in controlled experiments, and how game days and disaster recovery drills test the people and procedures as well as the systems.
MCQ: 10
Fill-in: 8
Flashcards: 11
Pair match: 10
Locked · 39 questions inside
6 more topics in this deck

Create a free account to open every topic — and play the whole deck without copying it.

Sign up freeLog in