Cloud // Software as a Service
News
2/25/2009
04:38 PM
Connect Directly
RSS
E-Mail
50%
50%

Coghead Failure Highlights Risks Of Cloud Computing

Cloud computing is growing, with Google now monetizing its App Engine. But no matter what the vendor, customers should have a good emergency-exit strategy.

Govind Davis, a Coghead customer, didn't see its sudden closing coming. Enticed by the cloud computing vendor's low-cost service, Davis built some of his customers' applications using Coghead's online database. Now his company, MCF Technology, has nine weeks to extract data from Coghead and build new applications for it, some of which will run on Intuit's QuickBase, also in the cloud.

Davis is still a huge proponent of cloud computing -- but a wiser one. "We'll be a little more wary with startups, as we realize the risk of going with one can be real," Davis said.

On Tuesday, a few days after Coghead said it was shutting down, a more widely known cloud vendor -- Google -- had a brief outage of its Gmail service because of a data center problem. Undaunted, Google announced that same day that it will start charging for Google App Engine, its Web-based application platform (or platform as a service).

No one should expect cloud computing to be infallible; software and servers never are, no matter where they reside. But Coghead's closure lends sobriety to the excitement surrounding cloud computing, which has attracted entrepreneurs big and small and fueled a new wave of venture capital in recent years.

Coghead's sudden closure also highlights the biggest gotcha of a platform as a service, software as a service, or anything else in the cloud genre: The vendor controls the systems and software. Coghead has told its customers their data needs to be out of its systems by April 30. If a traditional software vendor suddenly went belly up, at least its customers wouldn't face the pressure of a nine-week timeframe to find new software.

Choosing a stable vendor can reduce some of the risks of cloud computing. But even Google acknowledges that the migration path off the Google App Engine, should its customers want one, needs some work. "This is an issue, and we know it's not as easy as it should be," said product manager Pete Koomen.

Google offers an open source data-uploading tool, and to ease migration, will soon offer an open source downloading tool, Koomen said. Google supports the Python-based Django Web development platform, and if customers write their apps to conform with it, data portability is going to be the easiest, he added. Data portability "is something the team is very interested in and will make a lot of progress on going forward," Koomen said.

With Google's first-time payment structure for the previously free-with-quotas Google App Engine, customers pay 10 cents per CPU core hour, 10 cents per gigabyte of traffic in, 12 cents per gigabyte of traffic out, 15 cents per gigabyte of data stored per month, and $1 per 10,000 e-mails sent.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
8 Steps to Modern Service Management
8 Steps to Modern Service Management
ITSM as we know it is dead. SaaS helped kill it, and CIOs should be thankful. Hereís what comes next.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Must Reads Oct. 21, 2014
InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
A roundup of the top stories and trends on InformationWeek.com
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.