Site Reliability Engineering: A Field Primer
Notes from the Google SRE book, my own work experience and various resources online.
Contents
- What SRE Actually Is
- Core Vocabulary
- The Observability Triad
- Monitoring & Alerting Philosophy
- Incident Management
- Change Management & Deployment Safety
- Distributed Systems Fundamentals
- Data & State Management
- Networking Reality Checks
- Capacity Planning & Performance
- The Toolchain Landscape
- Chaos Engineering
- Security-Adjacent Concerns
- Org Patterns & Team Models
- Career Progression
- Essential Reading
- Week 1 Checklist
- Common Junior SRE Mistakes
1. What SRE Actually Is
Origin: Google, ~2003, when Ben Treynor Sloss founded the team on a specific premise — put software engineers in charge of operations, and they’ll solve operational problems the way engineers solve problems: by writing software that eliminates the problem, not by doing the manual task better by hand. That premise is still the core of the discipline.
Moving this place in a new direction. Less “tutorial about a thing I figured out”, more “notes for future me”. Articles are still there if you want them.
First Principles, Second-Hand Guides
I’ve been thinking about why i’d be (so as not to seem accusing anybody) awkward or straight up stressed out when throwing myself into things i haven’t done before.
my chronic anxiety contributes to part of that, but what contributed to my chronic anxiety in the first place?