Site Reliability Engineering (SRE) Handbook

How SRE implements DevOps

De: Stephen Fleming

Narrado por: Austin R Stoler

Duración: 2 h y 7 m

Resumen del Editor

Well, you have been hearing a lot about DevOps lately. Wait until you meet a Site Reliability Engineer (SRE)!

Google is the pioneer in the SRE movement, and Ben Treynor from Google defines SRE as, “what happens when a software engineer is tasked with what used to be called operations”. The ongoing struggles between development and ops team for software releases have been sorted out by mathematical formula for green or red-light launches!

Sounds interesting. Now, do you know which the organizations are using SRE? Apart from Google, you can find SRE job postings from LinkedIn, Twitter, Uber, Oracle, Twitter, and many more.

I also enquired about the average salary of a SRE in USA, and all the leading sites gave similar results: around $130,000 per year. Also, currently, the most-sought job titles in tech domain are DevOps and Site Reliability Engineer.

So, do you want to know how SRE works, what the required skill sets are, how a software engineer can transit to SRE role, how LinkedIn used SRE to facilitate the deployment process?

Here is your chance to dive into the SRE role and know what it takes to be and implement best SRE practices.

The DevOps, Continuous Delivery, and SRE movements are here to stay and grow. It's time you to ride the wave!

So, don’t wait! Take action!

©2018 Stephen Fleming (P)2018 Stephen Fleming

Don’t need to know your other books

This author spends too much time telling the listener about his other books and that SREs make 130k a year. There is not much here in terms of practical examples. The author doesn’t need to convince the listener SRE and DEVOps is the future. That’s why we are listening to the book. We want how in a handbook, not why.

informational

They read the table of context... why... Good handbook, but the reading is dry and literal

Excellent overview

In short and concise explanations, Stephen discusses the critically important things that drive what an SRE team should be designed to deliver.

dry, clueless performance, and not even helpful

Whomever thought that starting a book out with 15 minutes of reading the table of contents and all it's sub points was a good idea, should be forced to listen to this book. Austin's narration was very flat, but it's possible the extremely dry writing style of Stephen gave him little to work with. I have a 2 hour commute, and it took 3 trips before I finally gave up on this 2 hour 7 minute book, with 20 minutes still remaining. What did it in, was Stephen's lack of knowledge of what DevOps was, and talking about it as if it was a position or functional group like SRE is. That wasn't the worst part of the book, and I could overlook that, but it was the straw that broke the camel's back by the time it came up.

All prior reviews fake.

All created same day (1-5-2019) filled with a word salad of praise. Book isn’t read by a human, but obviously computer generated.

Avoid at all cost.

So bad than calling it awful is a compliment

I listened to books with bad narrators, but takes badness to a whole new level. Doesn’t even seems to be read by a human being.

If google had a feature to auto generate books based on results of google searches it likely would result in this book when searching SRE.