PDF: https://landing.google.com/sre/static/pdf/SRS.pdf
EPUB: https://landing.google.com/sre/static/pdf/srs-epub.epub
MOBI: https://landing.google.com/sre/static/pdf/srs-mobi.mobi
PDF: https://landing.google.com/sre/static/pdf/SRS.pdf
EPUB: https://landing.google.com/sre/static/pdf/srs-epub.epub
MOBI: https://landing.google.com/sre/static/pdf/srs-mobi.mobi
A bit far-fetched but: Have you (or anyone else at Google) looked at Amazon Builder's Library [0] and/or various re:Invent / re:Inforce talks from 2018/19 [1][2] that focus on similar topics as in this book and other SRE books? If so, what are some ideas (infrastructure, blast radius, incident management, resilience, recovery, deployment strategies, crisis management, disaster planning, aftermath etc) you folks think that contrast / complement Google's approach to building hyperscale systems?
Thanks.
[0] https://news.ycombinator.com/item?id=21714209
I haven't looked at those other resources, but I'll ask if others have.
$ tar -zxvf srs-epub.epub
gzip: stdin has more than one entry--rest ignored
tar: Child returned status 2
tar: Error is not recoverable: exiting now
But you can do "unzip srs-epub.epub".We use it here to help expand people's minds, shifting their thinking from just writing applications to designing for large-scale HA systems, with all the fun pitfalls that lurk in a cloud.
We wanted to write a book that focuses on integrating security and reliability directly into the software and system lifecycle, both to highlight technologies and practices that protect systems and keep them reliable, and to illustrate how those practices interact with each other.
We’d like to explicitly acknowledge that some of the strategies this book recommends require infrastructure support that simply may not exist where you’re currently working.
Because security and reliability are everyone’s responsibility, we’re targeting a broad audience: people who design, implement, and maintain systems. We’re challenging the dividing lines between the traditional professional roles of developers, architects, SREs, systems administrators, and security engineers.
Building and adopting the widespread best practices we recommend in this book requires a culture that is supportive of such change. We feel it is essential that you address the culture of your organization in parallel with the technology choices you make to focus on both security and reliability, so that any adjustments you make are persistent and resilient.
We recommend you start with Chapters 1 and 2, and then read the chapters that most interest you. Most chapters begin with a boxed preface or executive summary that outlines the following: • The problem statement • When in the software development lifecycle you should apply these principles and practices • The intersections of and/or tradeoffs between reliability and security to consider Within each chapter, topics are generally ordered from the most fundamental to the most sophisticated. We also call out deep dives and specialized subjects with an alligator icon."
(disclaimer: I work at Google)
(disclaimer: I worked on the book)
(Book author here)
(disclaimer: I worked on the book)
In the meantime, you can open it in a browser and email it to yourself. Not ideal, but a workaround.
[EDIT]: s/pursing/pursuing
https://www.amazon.com/gp/help/customer/display.html?nodeId=...