Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Cloud Reliability

Freshness Warning
This blog post is over 12 years old. It's possible that the information you read below isn't current and the links no longer work.

The web is all abuzz with angst and handwringing over yesterday’s two hour Gmail outage. Opinion pieces are cautioning people against relying on the cloud too much—after all if you stick all your data in the cloud and the provider goes down, you’re without access to your data. (For the record, I use Google Apps for two different domains and didn’t notice an issue.)

For most uses, however, cloud computing is not only more reliable, but safer than the alternatives. This outage primarily highlights the issue with large numbers of users flocking to a single service. When that service goes down, many people are affected.

Email servers go down all the time. Ask any employee of a small to medium company about the last time the "network" went down. Whether it’s the corporate Exchange server, a login server, or the actual network gear, brief issues and outages are not uncommon. You don’t hear about them simply because there are only dozens of users affected, not millions.

Most email systems don’t operate at web scale. They are localized (even in global, Fortune 500 companies mail servers are often geography specific) and can easily be brought down for maintenance during off periods. Gmail is a global app and likely doesn’t have any periods that can be considered off-peak. Considering that, Gmail’s uptime record is quite impressive.

Amazon’s nine hour outage from a few weeks ago and Gmail’s two hour outage yesterday aren’t ideal, of course. You’d rather have perfect reliability. But perfect reliability is a pipe dream. Google and Amazon have fearsome infrastructures and crack teams managing their services. They can afford the best of the best of everything and can recruit the best talent in the world. If they can have an outage, how much more likely is it that your in house IT staff and data center will have an issue? And which group would you trust more to recover quickly and ensure the issue doesn’t arise again?

On that same thread, what are the backup and disaster recovery practices like at your company or local email provider? Would you like to take bets as to whether Amazon or Google have better ones? Is your data more safe simply because it’s on your local network?

Companies and individuals relying on the cloud would be advised to back up their data and have plans for what to do in the event they lose their data or services. You shouldn’t rely on a third party to safeguard your critical data—after all, it’s your business that suffers if your data disappears. But using a solid cloud provider reduces the likelihood that you’ll ever actually need your backups.

Mary
August 18, 2008 9:50 PM

Not putting all your eggs in one basket should be the lessoned learned here.

stevenbshaffer
August 26, 2008 8:53 PM

Funny, I never noticed a problem. Believe me I would know. Gmail has become a life archive for me, it's not just email. Even still, I'm not worried. It has worked so well, for so long, and its free.

Jerry Loggins
September 1, 2008 11:22 AM

So many people have become hooked on their email that they would freak out if they couldn't access it for a while. The big problem is that they don't know how long it will be "down", and it is the unknown that freaks them out. If they KNEW it was only going to be down a couple of hours, they wouldn't get so upset. As for backing up files, you should always back up locally even if you do back up on the web somehow too. Backup your backup plan with another backup plan!

Donna
October 28, 2008 8:45 AM

I've always been uncomfortable trusting very important (business or personal) data to a service that is free. I'm not sure if it is because I am old school or just paranoid, but if a free service goes down for hours or just flat disappears, what recourse do you have? I've used Yahoo email since the 1980's and have had good service although there have been some bumps and bruises, including hacked accounts that are gone forever. Even with 20 years of service, I still don't trust Yahoo 100% and I can't imagine trusting Google for anything vital, either.

Dave
December 2, 2008 11:57 AM

I am a long time gmail user, and pretty much swear by it. I actually use it more than my corporate email, and I must say that the outage did not affect me at all. Actually it was somewhat of a blessing not having to think of emails for a couple of hours. Maybe the bigger issue here is that people are too consumed with these types of things, and should actually relish in the freedom of an outage. Just a though. Dave

This discussion has been closed.

Recently Written

How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.
Developer Experience Principle 5: Easy to Trust (Oct 9)
A developer building part of their business on your product needs to believe that you're going to do the right thing for them and their customers.
Developer Experience Principle 4: Easy to Get Help (Oct 8)
The faster you can unblock a stuck developer, the better their experience will be.
Developer Experience Principle 3: Easy to Build (Oct 5)
A product makes it Easy to Build by focusing on productivity for developers building real-world applications.
How to understand your product and your market (Sep 30)
A customer development question you can ask to find out who your product is best for and why they'll love it.
Developer Experience Principle 2: Easy to Use (Sep 28)
Making it Easy to Use means letting the developer do everything without involving you.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.