providers
(http://peterlaird.blogspot.com/2008/06/good-bad-and-ugly-of-saas-terms-
of.html) and it got me wondering: What about the emerging Platform as a
Service providers?
They've got an especially difficult challenge because they're running
other people's code. How do you ensure availability when it's not your
code? Google's App Engine conspicuously avoids the problem by not
providing any SLA.
Generally speaking, there seems be three categories of providers:
# Infrastructure, managed hosting and run time environments:OpSource,
Etelos, Joyent, AWS, GAE, etc
# Cloud IDEs: Bungee Labs, etc.
# App Builders: Coghead, LongJump, etc.
Obviously, the closer you get to bare metal, the harder it is for you to
provide service guarantees.
AWS provides for 99.9% in their SLA, but that's only for the service
itself. Nowhere in this document does it say anything about your image's
uptime. Seems that you are on your own entirely.
http://www.amazon.com/S3-SLA-AWS/b?ie=UTF8&node=379654011
This is a tricky problem even for the app builders. They all support
some kind of scripting environment and you can only sandbox so much. Not
to pick on CogHead, but I found this post on their forum. So, as you can
see, these problems are going to show up everywhere.
http://blogs.zdnet.com/SAAS/?p=489
I'd love to hear from anyone that has more details on SLA from platform
providers.
Original Blog Post http://blog.snaplogic.org/?p=201
__________________________________
Chris Marino
SnapLogic, Inc.
Really Simple Integration
www.snaplogic.com
650-655-7200
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cloud Computing" group.
To post to this group, send email to cloud-computing@googlegroups.com
To unsubscribe from this group, send email to cloud-computing-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.ca/group/cloud-computing?hl=en
-~----------~----~----~----~------~----~------~--~---
Posts
No comments:
Post a Comment