Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Cloud Reliability

Freshness Warning
This blog post is over 16 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.

Recently Written

Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.
Product Add-Ons Are An Expansion Myth
Dec 1: Add-ons can enhance your product’s appeal but won’t drive significant market growth. To expand your customer base, focus on developing standalone products.
Protecting your Product Soul when the Same Product meets New People.
Nov 23: Expand into new markets while preserving your product’s core value. Discover how to adapt and grow without losing your product’s soul.
Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.

Older...

What I'm Reading