Thursday, July 31, 2008

Software as a Service for ISVs - Final

How many definitions of Platform as a Service (PaaS) have you come across with? Maybe you've read about Saugatuck's opinions or if you're a wiki-lover, you've read this. And definitely, if you've followed Morph Labs closely, you would have stumbled on this podcast or the three layers of cloud computing.

It is much a buzzword just as "in the cloud" is. In this post, how about we just give you analogies?

Analogy 1. You need transportation to get you from your house to work. Now, would you get an engine, a set of wheels and a chassis? You could assemble these into transportation, but do you really want to spend your time doing that? Do you have the skills to do it?

On the other hand, platform as a service providers offer you a car. You just get in and drive to work. Now apply this to applications. Morph Labs' value proposition is that our environment is ready to accept the application, removing the tasks of configuring/setting up servers, load balancers and databases. You could build a system on Amazon EC2, for instance to deliver a Grails application, but then you are spending your time building out the delivery platform. This also assumes that as a developer, you understand how to build out such an architecture to ensure that your applications are available, are backed up properly and are serviced over the long run.

Here is a link to Cleve Gibbon's article mentioning this analogy.

Analogy 2. Think of platform as a service as a fully serviced office. You just pick a package, move right in and get to work. You'll have a desk to work on, you're equipped with connectivity, and you'll even have people to help you manage incoming calls. In addition, you won't even have to think about facility maintenance.

So there you go. And yes, let me say this: don't take our word for it. BUT do hear out what our customers say about us.

Send us an email at info at mor dot ph if you'd like to know more about our services. OH! Here's a link to the webinar that I mentioned in the previous post.

No comments: