Is there a more digestible version of SRE concepts somewhere?
I'm just looking for an easier way to communicate core principles and concepts to my team without asking them to sink into 500 pages?
I'm just looking for an easier way to communicate core principles and concepts to my team without asking them to sink into 500 pages?
The second book (the SRE workbook) is more prescriptive, walks through practical ways of implementing it.
The most base description of SRE principles is simply that:
1) You automate aggressively and develop or use self-service tools as much as possible (over ops work)
2) you define what “availability” really means; institute an allowance of errors based on budget. Highly reliable systems should get much more attention and budget than lower requirement systems. Make an SLO dashboard; alert based on your “error budget” being eaten too quickly.
3) try to avoid allowing your staff to work more than 50% on operations work; that’s your indicator for being overloaded.
SRE Workbook (https://landing.google.com/sre/workbook/toc/): Chapters 1, 2, 5, 6, 8, 16, 17, 19, 20, 21, All the Appendixes
Disclaimer: I work for Google
https://www.usenix.org/conference/srecon14/technical-session...