Comment on Stripe Blog: Track Stripe's uptimeparentComments−latchkey14yI don't see a SLA for Stripe on the ToS page, why not?GAE has actually had 100% uptime for the last year. http://googleappengine.blogspot.com/2012/01/happy-birthday-h...−moe14yI don't see a SLA for Stripe on the ToS page, why not?Blanket SLAs are not normally worth the paper they're written on. Look up the breach-compensation for your favorite TOS-SLA sometime.Publishing the uptime history is a much more honest approach. Kudos to stripe for doing just that.−latchkey14yI'm not knocking them for publishing their failures. That is all great.I'm questioning the comparison with other unrelated systems that are much bigger than them, especially when they don't publish a SLA themselves.−moe14yWhy should they publish an arbitrarily chosen figure in addition to telling you the actual figure?−pestaa14yThat is a really good way to put it, but I can't seem to ignore the abscence of an important business document. It feels like the arbitrarily chosen figure is step 1, the actual figure is step 2, and they just skipped the first half.−pc14yThat blog post refers to their high-replication datastore, not GAE as a whole.
Comments
I don't see a SLA for Stripe on the ToS page, why not?
GAE has actually had 100% uptime for the last year. http://googleappengine.blogspot.com/2012/01/happy-birthday-h...
I don't see a SLA for Stripe on the ToS page, why not?
Blanket SLAs are not normally worth the paper they're written on. Look up the breach-compensation for your favorite TOS-SLA sometime.
Publishing the uptime history is a much more honest approach. Kudos to stripe for doing just that.
I'm not knocking them for publishing their failures. That is all great.
I'm questioning the comparison with other unrelated systems that are much bigger than them, especially when they don't publish a SLA themselves.
Why should they publish an arbitrarily chosen figure in addition to telling you the actual figure?
That is a really good way to put it, but I can't seem to ignore the abscence of an important business document. It feels like the arbitrarily chosen figure is step 1, the actual figure is step 2, and they just skipped the first half.
That blog post refers to their high-replication datastore, not GAE as a whole.