"Error budgets" are the god-damn worst idea I've heard of in recent years. SLAs should be realistic goals about what we can achieve with our current techniques and tools, not permission to fail a certain amount.
-
-
If you measure your SLA (or error budget) in terms of % successful transactions rather than wall clock time then they become much more meaningful to everyone.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Planned maintenance aside, plenty of companies other than Amazon optimise for rapid evolution over availability. Explicitly calling that trade off out and being clear about it with stakeholders is a wonderful idea
-
Being able to express to stakeholders that if they want a team to get their features out quickly they may have to sacrifice some reliability is important. Error budget is just one way to expose it
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.