Between the Lines

Larry Dignan, Andrew Nusca and Rachel King

Platform as a service and redundancy: Nagging questions

By | May 18, 2011, 2:30am PDT

The recent Amazon Web Services outage along with other cloud mishaps of late is raising questions about platform as a service maturity, lock-in and customer recourse.

Since the AWS outage, I’ve been pondering platform as a service. With AWS, which is essentially infrastructure as a service, it’s not-too-difficult to imagine having another provider as a backup. Commodity APIs mean it’s at least theoretically possible to swap in Rackspace for AWS. Or in the future it’s HP’s public cloud. With the right cloud management tools it’s should be a relatively easy swap.

As you move up the cloud stack the outage worries pick up. For instance, let’s lay out the following scenario.

  1. An enterprise picks a platform as a service provider—Microsoft’s Azure or Salesforce.com’s Force.com for instance.
  2. That platform works fine most of the time, but…
  3. It happens to blow up for a few days just like AWS did.
  4. Enterprise is locked into a platform that doesn’t work.
  5. Platform as a service providers to date can’t talk to each other. These platforms are proprietary. You can just swap Azure to Force.com. And guess what you probably never will. You’re betting on a platform, a language and that company’s ability to keep running.

BMC CTO Kia Behnia says that the scenario outlined above does highlight the immaturity of platform as a service today. “Infrastructure as a service is a bigger market and use case,” says Behnia. “PaaS is growing up. It will have its place in focused areas but you can’t just tell enterprises to part with their code and trust the vendor. PaaS is in its infancy.”

Okta CEO largely agrees. Okta survived the AWS outage because it was architected to fail over to other parts of AWS. With IaaS it’s clear that reliability depends on the provider. “As you move up the stack it’s not as clear,” says Todd McKinnon. “What is the SLA for platform as a service?”

Those nagging questions continue. A bevy of enterprise execs at SAP’s Sapphire said that they were wary of platform as a service, but they had no worries about infrastructure in the cloud. Perhaps these IT buyers will come around. Today, they remain wary.

Ultimately, developers will vote with their code, but platform stability will matter big time. And PaaS vendors will have to demonstrate they have an extremely reliable system.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Larry Dignan is Editor in Chief of ZDNet and SmartPlanet as well as Editorial Director of ZDNet's sister site TechRepublic.

Disclosure

Larry Dignan

Larry Dignan has nothing to disclose. He doesn’t hold investments in the technology companies he covers.

Biography

Larry Dignan

Larry Dignan is Editor in Chief of ZDNet and SmartPlanet as well as Editorial Director of ZDNet's sister site TechRepublic. He was most recently Executive Editor of News and Blogs at ZDNet. Prior to that he was executive news editor at eWeek and news editor at Baseline. He also served as the East Coast news editor and finance editor at CNET News.com. Larry has covered the technology and financial services industry since 1995, publishing articles in WallStreetWeek.com, Inter@ctive Week, The New York Times, and Financial Planning magazine. He's a graduate of the Columbia School of Journalism and the University of Delaware.

For daily updates, follow Larry on Twitter.

4
Comments

Join the conversation!

Just In

RE: Platform as a service and redundancy: Nagging questions
kidneyy 9th Oct
Woah! I'm really loving the template/theme of this website. It's simple, yet effective. A lot of times it's very difficult to get that "perfect balance" between user friendliness and appearance. I must say you've done a excellent job with this. Also, the blog loads very fast for me on Firefox. Outstanding Blog! pregnancy week by week pictures
0 Votes
+ -
Cartel-like
johnfenjackson@... 18th May 2011
"Platform as a service providers to date can?t talk to each other."

Indeed, and they are not likely to provide interoperable designs, operating more like a cartel keeping the price of the cloud uniformly high amongst a few big players.
What about a PaaS broker? I service that sits in the middle acting as a Y-valve...as one PaaS provider goes down, the valve diverts the traffic. The API written to is the broker, not the provider...
WONDERFUL Post.thanks for share..extra wait .. ??? katy perry
Woah! I'm really loving the template/theme of this website. It's simple, yet effective. A lot of times it's very difficult to get that "perfect balance" between user friendliness and appearance. I must say you've done a excellent job with this. Also, the blog loads very fast for me on Firefox. Outstanding Blog! pregnancy week by week pictures

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix