3 ms·
Actually, 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
by jpatokal 10y ago
Actually, 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.