Buy:Prednisolone.Retin-A.Accutane.Zyban.Human Growth Hormone.Mega Hoodia.Arimidex.Actos.Zovirax.Synthroid.Prevacid.Nexium.100% Pure Okinawan Coral Calcium.Petcam (Metacam) Oral Suspension.Valtrex.Lumigan….

Categories: Stop SmokingAntidepressants.Blood Pressure/Heart.Mens Health.Skin Care.Antidiabetic.Vitamins/Herbal Supplements.Stomach.Pain Relief.Womens Health.Eye Care.Anti-allergic/Asthma.Weight Loss.Antiviral.Mental HealthAnxiety/Sleep Aid.Antibi…

Thanks!…

Thanks for you comments and questions. Yes, marketing as usual has created a lot of buzz word and left us regular folks to figure things out. I will try to answer your questions and yes, will try my best in future to put my own understanding here.

1. ASP is old news. The main difference as I understand is that ASP could be any software that is hosted on someone’s else infrastructure. The concept of multitenant was not important for a ASP. Each client could be installed on a separate set of servers. Most of the time, the domain would be specific to the client, for example company1.aspname.com or company2.aspname.com

SaaS is purely multitenant. Another great example which you are familiar with is Zimbra. Zimbra is providing a replacement of traditional email servers installed and maintained by enterprises.

2. Neither. You are renting a virtual server from go-daddy. A Server is a blank canvass for you to draw your masterpiece. This comes more under Utility computing, IMHO.

3. Gmail is a application, so I would put that under SaaS and yes, SaaS is a subset of Utility. IMHO again.

And as per your final, 1, 2 comments, yes, SaaS is just a fancy name.

Having a client_id is a great start but does not make an application ready to provided to multiple clients. I am sure you would agree with me on that.

The excitment around SaaS is more in the economic implications and how it will change the enteprise computing. I remember when big companies stayed away from salesforce, but now I am surprised many are not just using but also integrating with some of their internal applications. As this gets adopted I am sure other enterprise software that are not truly part of an organization’s true competitive advantage will also go the SaaS way.

(Maybe these are good candidates for future posts since a lot of folks I know have gone through the same confusion).

Question 1 –

I’m particularly confused between marketing buzz-words and their differences. What’s SAAS and what’s ASP and what’s the key practical differentiating factor? What are some famous SAAS sites out there and what are some famous ASP sites out there and how are they different.

(Wikipedia offers some help here - http://en.wikipedia.org/wiki/Software_as_a_Service - but I think it lacks explanation with real life examples).

Question 2 –
>Multi-tenant is not the same as virtualization, a misconception spread by even the gurus in this world. Virtualization is the ability to slice hardware to represent multiple virtual machines.

Yes, but Virtualization can be SAAS’ed right? So If I bought a virtual server from Go-Daddy would you refer to it as SAAS or ASP?

Question 3-

> Providing computing resources including software, storage or hardware as subscription based service is utility computing

When I register for a free Gmail account is that SAAS too? Isn’t Gmail providing software, storage and hardware for it in return of my subscription (in Google Apps or free in Gmail). Would you also call it utility computing?

From your post it appears like SAAS is really a sub-set of utility computing. Did I understand that correctly?

If yes, what’s an example of SAAS that’s not utility computing?

And now some questions which makes me take words like SAAS, Utility Computing, Grid computing and others with a pinch of salt:

1. If the click here to register for a Web-application is SAAS that’s been around for years, right? Why are we suddenly giving them these fancy names and talking about them?

2. I was building web-applications that had a client-id column in a database somewhere; I’ll continue to build web-applications with a client-id column in a database somewhere, which I will now call SAAS and everyone will get excited. Is that really what SAAS is all about or is there something that we really need to learn and pickup as developers. Something that we might be missing out on. As a developer; are there additional concepts I should know or care to learn?