4 ms·
I read halfway through the book. I was also on a SRE team at Google. Some of my ex teammates co-authored or contributed to this book. I think that much of what
by nunez 10y ago
I read halfway through the book. I was also on a SRE team at Google. Some of my ex teammates co-authored or contributed to this book.
I think that much of what Google is espousing is only applicable to companies like Google, I.e. Technology companies with billions in the bank to spend on extra nine's.
The "problem" is much more fundamental. Most businesses still feel that technology is a cost to debit against the business. As long as those in charge feel this way, the issues that necessitate a book like this will continue to persist.
- yeukhon 10y agoI have a different perspective. The fundamental issue with many IT departments out there is the people managing the IT department out there or the people working in the department. The cultural difference between the young and the very traditional IT are in conflicts. Finding the right talents (sigh every time someone said let's look for someone with scripting experience - no...please look for someone with software engineering experience).
- nunez 10y agoI agree that disconnects between management and the "boots on the ground" are part of the problem here.
- bogomipz 10y agoCan I ask what is the level of software engineering vs systems engineering they want or expect for the SRE role?
- cdjones 10y agohttps://www.usenix.org/publications/login/june15/hiring-site-reliability-engineers https://www.usenix.org/publications/login/june15/hiring-site... might be interesting on that point.
- bogomipz 10y agoThanks, this is a good read in and of itself. It's rather vague about the software engineering bar unfortunately. Basically it just says that one of the interviews they do is coding.
- jeremyjh 10y agoThe book talks about this. They hire some engineers with traditional software engineering experience - people who have worked developing features on a product team. But they also ensure they hire some percentage (40-50% I think) of team members who have some software experience but also have sysadmin or network engineering experience.
- bogomipz 10y agoThanks, I hope to find some time to read through this. Cheers.
- nunez 10y agoAt Google they are mostly one in the same I.e. Software engineers who know significant amount about systems.
- jpatokal 10y agoActually, one of the points emphasized by the book is that extra nines cost significant amounts of money and you need to figure out your optimal SLO accordingly. I recently worked with a client who was OK with one 9, because they valued rapid development above all other things. Not many would make this trade-off consciously, but they did and it worked for them.
- sokoloff 10y agoGreat point! I set the target at "three nines five (99.95%)" at one place and had to defend why I wasn't aiming higher. "Because I think we can get it consistently there with minimal drag on engineering. To get substantially higher than that, I think I need to start setting policies that will slow down engineering and that makes no sense." Also, at the time, we had outages almost every week. At the worst of it, we used to joke that we were "chasing our second eight of uptime..."
- paulddraper 10y agoExactly this. That's 9 hours a year, or 43 seconds a day. Any higher than that, and you have to do LOTS of extra engineering. Hell, I doubt even places like Github and Twitter did much better than that last year (e.g. Dyn).
- nunez 10y agoYou are right; the cost of reliability is definitely talked about in the book.
- solatic 10y ago> Most businesses still feel that technology is a cost to debit against the business Isn't this one of the reasons why SRE is so important? The monitoring that SRE builds helps to quantify these costs so that rational decisions can be made by upper management regarding the appropriate amounts to invest and where, instead of the finger-in-the-wind biased estimations most businesses use. > Only applicable to companies like Google Will most companies achieve or need a level of reliability that Google needs? No. But in the same way which user stories force product managers to have actual conversations with their users about what features are really necessary and which are just part of some kitchen-sink wish list, so too does SRE force management to have actual conversations regarding the real amount of reliability their products need and the costs of not respecting that target, either by spending too much to achieve a level of reliability which is ultimately unnecessary for the business strategy, or by spending too little and leaving money on the table by turning off users who are being served with an inferior product.