Comments on: Bacon Bits & SaaS: Imitatations are Tasty, But the Real Thing is Better

By: malathi

malathi — Fri, 22 Jan 2010 10:01:43 +0000

I wanna do a mini-project in SaaS.FOr that,I need to know the routing phenomenon taking place in SaaS.i.e.from user requesting the software to the request reaching the cloud where the requested software resides.Can you help me?

By: Jay

Jay — Fri, 07 Aug 2009 17:15:20 +0000

Very good explanation on SaaS. I am glad that you included SaaS is not always more cost effective than others unless it is implemented correctly. The Provider must take advantage of the economies of scale. This is often overlooked. I can certainly say with hosting a SaaS application ourselves that this is always looked at when enhancing the product for the end user. We always want to ensure that the software has the least over head as possible and is why our company has succeeded in driving the cost down for church management software verses the non-SaaS counter parts. While the end user’s prospective is important there is no model within the software industry that will satisfy everyone. The end users in the church industry for example have very different ways of doing things and some need certain features while others do not. Will a SaaS system or any other system have every feature they are looking for - probably not. Just a subtle point to make.

By: Virtualize this

Virtualize this — Tue, 21 Jul 2009 00:37:18 +0000

[…] in the dot com years and even that experience did not prepare me for the unique challenges of the “single instance, multi-tenant” model that drives SaaS software. At this point, our architecture is highly distributed and we know […]

By: Daily Concerns : Evaluating the various Church Software SaaS Offerings

Daily Concerns : Evaluating the various Church Software SaaS Offerings — Mon, 28 Jan 2008 21:23:39 +0000

[…] A cursory review of articles on the Internet yields some common threads — a �true’ SaaS utilizes “a single production environment to support all customers” or put more succinctly “single instance, multi-tenant.” The evolution of SaaS from the Application Service Provider model (delivering hosted client applications via tools like Citrix) to today’s model of web-native, multi-tenant, applications also reinforces this concept.Regardless, I believe the key consideration is this — are all SaaS delivery methods considered equal to both the provider (scalable, efficient, profitable) and the end user (ease of use, accessibility, cost)? A great article on this topic can be found at SaaSBlogs.com: What is SaaS? The Answer is Rooted in the End User. In the article, the author contends that the best way to define SaaS is from the end user’s perspective — are their needs satisfied by the vendor’s chosen delivery model? However, the end user must also consider the viability of the vendor’s model. The author goes on to state that “the most successful providers will leverage multi-tenant, single instance because it provides maximal efficiency and value derivation.” […]

By: SaaS Blogs - » What is SaaS? The Answer is Rooted in the End User

SaaS Blogs - » What is SaaS? The Answer is Rooted in the End User — Fri, 01 Dec 2006 21:07:39 +0000

[…] ��One thing I noticed was the frequent mingling of concerns and perspectives when it came to the debate. In my mind, SaaS can be looked at from one of two perspectives that define the economic, use, and definition boundaries of the distribution model: End User and Provider. When we are trying to define SaaS, we need to understand that the basic definition comes from the End User Perspective, not the Provider Perspective. In terms of a purist definition, this perspective is relatively void of implementation concerns (which should be filed under the Provider Perspective). This makes it difficult for me to agree with the concept that there is a SaaS litmus test whose primary indicators stem from the Provider Perspective. Recently I blogged about “imitation SaaS” and “true SaaS”, but I should have defined the terms to indicate implementation approaches. The article does this, but alas, the two prevalent terms fail to highlight the provider perspective as a context. To summarize the notions of perspective, I mocked up the following diagram: […]