6 ms·
Getting Google Apps to 99.99%
- ghshephard 16y ago99.984% Availability in 2010 is an absolutely incredible accomplishment, and the Google Team deserves a ton of accolades. They are making two (2) changes for 2011: o Removing scheduled downtime - that's now included in their SLA. That's Huge. o Removing transient outages from their downtime - an outage of a few minutes is now included in their downtime calculations. This sets the bar for the industry in terms of what type of availability they need to shoot for enterprise class SaaS. Nice to see Google pushing the envelope here.
- eitally 16y agoWhat they haven't published is their definition of downtime. With close to 200 million users globally, how many have to be affected and for how long before it's considered an outage? If you're a business customer with 20,000 users and you regularly have one or two suffering the 24hr account outage for maintenance, it's a tiny percentage of Google's population but if it's the wrong individuals it can wreak havoc.
- brown9-2 16y agoSounds to me like they're counting up all requests in total and determining which of them experienced some issues, and then labeling that downtime. The translation into minutes is really in a different type of units. The fact that they're including delays of just a few seconds is what makes me think this.
- uggedal 16y agoFor anyone curious, 99.984% uptime works out to 84 minutes of downtime over one year.
- detst 16y agoAsk Google, (100-99.984)% of 1 year in minutes and it will tell you: (100 - 99.98400)% of (1 year) = 84.1518026 minutes I'm sure many here will already know that they can do this but I do so many calculations like this with Google that I'm sure it will be a benefit to someone reading this.
- mikeknoop 16y agoThis article made me contemplate that pure uptime percentage is not the best way to measure availability. Surely having 5 to 10 second outages 10 times a month is better than having a single outage for 4 hours?
- corin_ 16y agoWhile your second statement is true, uptime percentage remains the best way until somebody suggests a new (feasible) method.
- hammerdr 16y agoA combination of both uptime percentage and mean outage time (or mean time between outages.. which is essentially the same thing).
- wmf 16y agoYes, that's why many SLAs do not count short outages.
- ceejayoz 16y agoI'd be pretty mad if that was in my SLA, unless it was very carefully worded. If the system's going down for a minute every hour or two, it's probably more of a disruption to me than if it goes down for an hour or two once a month.
- lutorm 16y agoI don't understand your point: 10 x 10s outages = 100s downtime. One 4h outage = 14000s downtime. Uptime percentage agrees with you that the former is better.
- mikeknoop 16y agoSorry for the poor math -- You would have to have roughly 100 10 second outages each month to approach a 4 hour outage one a year.
- deleted 16y ago[deleted]
- melling 16y agoI want the bleeding edge version that is only up 90% of the time where they keep adding features. Let's call it the nightly build version. Google might also consider letting people subscribe to a version that only supports very modern browsers. FF4, IE9, etc. This will create a beta channel for "release early, release often."
- hughw 16y ago"Email is much more complex than your home phone..." That doesn't seem like a slam dunk obvious truth to me. The PSTN is no mean feat either.
- vegai 16y agoMicrosoft BPOS -- I can come up with a few ways to expand that.