{{ searchResult.published_at | date:'d MMMM yyyy' }}

Loading ...
Loading ...

Enter a search term such as “mobile analytics” or browse our content using the filters above.

No_results

That’s not only a poor Scrabble score but we also couldn’t find any results matching “”.
Check your spelling or try broadening your search.

Logo_distressed

Sorry about this, there is a problem with our search at the moment.
Please try again later.

If one trend has captured the hearts and minds of internet executives, entrepreneurs and developers alike over the past several years, it's cloud computing. And when it comes to market leaders, at the front of the pack is Amazon.

Its suite of offerings, known as Amazon Web Services (AWS), has attracted some of the most prominent consumer internet services, including Twitter, as well as a slew of up-and-coming startups looking for the ability to scale in their early days without Facebook-like funding. Through its cloud, companies can do everything from run resource-intensive applications to send high volumes of email.

On paper, the potential benefits of cloud computing are undeniable, but the cloud, and its most visible providers, aren't perfect.

Last week, Amazon's EC2 service had a major meltdown which didn't just cripple EC2 users, but brought some of them to their knees. Sites taken down for the count included Foursquare, Quora, Reddit and Hootsuite (and its owl.ly URL shortener).

Perhaps most embarassing, the homepage of Ruby cloud platform provider Heroku, which was recently acquired by Salesforce.com for more than $200m, served up nothing more than this ugly error message:

In the cloud, when it rains it pours.

So has Amazon's torrential rain of fail exposed the cloud as an emperor without clothes? Perhaps surprisingly, the answer is 'not really.' What it does expose: poor infrastructure and application architecture.

Noting that Amazon EC2 is available in multiple locations, and that the major failure was at one of them, Bob Warfield, writing on behalf of the Enterprise CIO Forum and HP, pointed out:

Most SaaS companies have to get huge before they can afford multiple physical data centers if they own the data centers. But if you’re using a Cloud that offers multiple physical locations, you have the ability to have the extra security of multiple physical data centers very cheaply.

The trick is, you have to make use of it, but it’s just software. A service like Heroku could’ve decided to spread the applications it’s hosting evenly over the two regions or gone even further afield to offshore regions.

In other words, the companies that were affected by the problems in Amazon's Northern Virginia data center put their applications (or critical pieces of their applications) into the cloud, but never realized (or ignored) the fact that they still had done nothing to prevent the creation of a single point of failure. That's a huge mistake, but it's also a mistake you wouldn't expect a seasoned CTO to make.

The lesson here is clear: the cloud, with all of its virtues, still requires thoughtful, informed and strategic technical leadership if it's to be used effectively. The problem with the cloud then clearly isn't that systems and networks will go down (they always will), but rather that there may be far too much of a "It's in the cloud, therefore it's okay" mentality. For the sake of the companies using the cloud, and the cloud itself, that has to change.

Part of effecting that change may entail giving a little bit less responsibility to developers. Many companies that do everything (or almost everything) in the cloud rely on developers to manage a huge portion of their technology stack.

In reality, this is usually a bad idea, as different layers of the stack require different knowledge and skill sets. Most developers, for obvious reasons, don't have mastery of all the layers, so Amazon's blowup reminds us that letting developers architect everything is a recipe for disaster.

Patricio Robles

Published 26 April, 2011 by Patricio Robles

Patricio Robles is a tech reporter at Econsultancy. Follow him on Twitter.

2365 more posts from this author

Comments (6)

Comment
No-profile-pic
Save or Cancel
Avatar-blank-50x50

Liam McCoy

The cloud really is the future, but no future comes without a few bumps. Kudos to Amazon for being a leader in the field. They've been doing things I would have expected from Apple or Google first.

about 5 years ago

Avatar-blank-50x50

Rene Power

Smart post Patricio and a timely reminder of the risks of building a business and over relying on others to help deliver it.

Surely, you would have a contingency plan for something like this. I, like millions of others, was affected.

Like Liam I'm a little surprised that it was Amazon who trail blazed in this area but I guess they saw the opportunity first.

about 5 years ago

Avatar-blank-50x50

Jeffrey Golby

Like all, I was stunned when the Cloud failed on friday. However, unlike when my local servers would fail in the past, I knew Amazon had some of the BEST people working on it and therefore I knew that they would get it up as soon as possible. The article also hits the nail on the head with saying - why the heck would you have EVERYTHING in one location. We were spread out over multiple sites and thus the part that made us money - never went down. Learn as we go eh?

about 5 years ago

Stephen Thair

Stephen Thair, Director at Seriti Consulting

Interestingly the "Devops" movement would draw an opposite conclusion - they think that Developers should be MORE involved in Operations (hence Devops).

http://www.jedi.be/blog/2010/02/12/what-is-this-devops-thing-anyway/

Conversely, some people think that Devops is a load-a-hokum...

http://teddziuba.com/2011/03/devops-scam.html

Still, it's well worth people thinking about how they hand the transition from Dev to Ops in a better way!

about 5 years ago

Fran Jeanes

Fran Jeanes, Internet Business Consultant at i-contact web design

The problem comes when all your eggs are in one basket, and that basket gets dropped. Understandably it is very costly to pay for multiple data center storage, however, I think that Plan B is now seen as more of a necessity, than a maybe, after such a long AWS downtime. Better it be a wake up call for the big guys now, than when they get even bigger.

about 5 years ago

Clint Davis

Clint Davis, Web Services Manager at Gray Loon Marketing Group, Inc.

"...didn't just cripple EC2 users, but brought some of them to their knees."

What's the difference?

about 5 years ago

Comment
No-profile-pic
Save or Cancel
Daily_pulse_signup_wide

Enjoying this article?

Get more just like this, delivered to your inbox.

Keep up to date with the latest analysis, inspiration and learning from the Econsultancy blog with our free Daily Pulse newsletter. Each weekday, you ll receive a hand-picked digest of the latest and greatest articles, as well as snippets of new market data, best practice guides and trends research.