<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SaaS: All PaaS are Not Created Equal</title>
	<atom:link href="http://blog.sciodev.com/2009/03/27/saas-all-paas-are-not-created-equal/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sciodev.com/2009/03/27/saas-all-paas-are-not-created-equal/</link>
	<description>Hot Thoughts about SaaS, On-Demand Business and Technology</description>
	<lastBuildDate>Mon, 30 Jan 2012 15:58:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michael Dunham</title>
		<link>http://blog.sciodev.com/2009/03/27/saas-all-paas-are-not-created-equal/comment-page-1/#comment-818</link>
		<dc:creator>Michael Dunham</dc:creator>
		<pubDate>Mon, 31 Jan 2011 16:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=408#comment-818</guid>
		<description>Ron - Sorry for the delay in answering but... The main consideration is &quot;What do you want the platform to do for you?&quot;  If it is just to provide a coding platform that includes the database, OS and language runtimes as transparently as possible, there are many platforms available from major hosting providers. If on the other hand, it is to provide as transparent a scaling platform as possible, Microsoft Azure (perhaps surprisingly but never the less) can work with LAMP implementations. But - there isn&#039;t anything LAMP specific  that I am aware of to solve the more operational side of SaaS - meaning billing, multi-tenancy, implementation, etc. That said, you can leverage services to replace the some effort required to code the operational side of SaaS regardless of your choice of approaches and with LAMP - that may be what you need to consider. I&#039;m thinking of billing, pricing, settlement - all the little things that mean you can actually take care of day to day operations.  

The main point to consider is your scalability and reliability over the lifecycle of the application.  Of course, as programmers we know that nothing is &quot;cemented&quot; in place, but the effort we&#039;ve spent on core development is often hard to offset while we&#039;re ramping up for a growth curve. If there is anything about your core that could limit your ability to implement new customer instances transparently, to operate and maintain the application without downtime - it is a constaint you may find you cannot afford.  There is nothing inherent in a LAMP approach that would limit a company but those that use it often find it difficult to make business tradeoffs to lower development effort and bring a solid application to market.</description>
		<content:encoded><![CDATA[<p>Ron &#8211; Sorry for the delay in answering but&#8230; The main consideration is &#8220;What do you want the platform to do for you?&#8221;  If it is just to provide a coding platform that includes the database, OS and language runtimes as transparently as possible, there are many platforms available from major hosting providers. If on the other hand, it is to provide as transparent a scaling platform as possible, Microsoft Azure (perhaps surprisingly but never the less) can work with LAMP implementations. But &#8211; there isn&#8217;t anything LAMP specific  that I am aware of to solve the more operational side of SaaS &#8211; meaning billing, multi-tenancy, implementation, etc. That said, you can leverage services to replace the some effort required to code the operational side of SaaS regardless of your choice of approaches and with LAMP &#8211; that may be what you need to consider. I&#8217;m thinking of billing, pricing, settlement &#8211; all the little things that mean you can actually take care of day to day operations.  </p>
<p>The main point to consider is your scalability and reliability over the lifecycle of the application.  Of course, as programmers we know that nothing is &#8220;cemented&#8221; in place, but the effort we&#8217;ve spent on core development is often hard to offset while we&#8217;re ramping up for a growth curve. If there is anything about your core that could limit your ability to implement new customer instances transparently, to operate and maintain the application without downtime &#8211; it is a constaint you may find you cannot afford.  There is nothing inherent in a LAMP approach that would limit a company but those that use it often find it difficult to make business tradeoffs to lower development effort and bring a solid application to market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald Meaux</title>
		<link>http://blog.sciodev.com/2009/03/27/saas-all-paas-are-not-created-equal/comment-page-1/#comment-816</link>
		<dc:creator>Ronald Meaux</dc:creator>
		<pubDate>Tue, 18 Jan 2011 05:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=408#comment-816</guid>
		<description>We are an ISV startup working on a new multi-tenant application built in PHP. Which PaaS providers would you suggest for a LAMP stack offering?</description>
		<content:encoded><![CDATA[<p>We are an ISV startup working on a new multi-tenant application built in PHP. Which PaaS providers would you suggest for a LAMP stack offering?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Waldrum</title>
		<link>http://blog.sciodev.com/2009/03/27/saas-all-paas-are-not-created-equal/comment-page-1/#comment-106</link>
		<dc:creator>Scott Waldrum</dc:creator>
		<pubDate>Thu, 02 Apr 2009 22:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=408#comment-106</guid>
		<description>I like that you&#039;ve looked at this from an operational perspective as opposed to a development platform perspective. Having spent time running Product Management but also operations for some SaaS start-ups lately, your list really resonates. Interestingly, the major players in what we seem to be calling the PaaS space these days aren&#039;t addressing your list very well. I&#039;m quite certain they&#039;ll get there and you see them beginning to dip their toes in the billing space. If you put monitoring and provisioning aside, your list really comes down to subscriber management and billing. There are some really interesting companies that solve these problems that haven&#039;t really been considered PaaS players to date. Some have been doing this for some time like &lt;a href=&quot;http://www.ipapplications.com&quot; rel=&quot;nofollow&quot;&gt;IP Applications&lt;/a&gt; and Aria while others like &lt;a href=&quot;http://www.zuora.com&quot; rel=&quot;nofollow&quot;&gt;Zuora&lt;/a&gt; are startups generating a fair bit of buzz. I think we&#039;re going to see a bit of consolidation here as the big PaaS players realize the scope of the operations problem they need to solve to really provide value...</description>
		<content:encoded><![CDATA[<p>I like that you&#8217;ve looked at this from an operational perspective as opposed to a development platform perspective. Having spent time running Product Management but also operations for some SaaS start-ups lately, your list really resonates. Interestingly, the major players in what we seem to be calling the PaaS space these days aren&#8217;t addressing your list very well. I&#8217;m quite certain they&#8217;ll get there and you see them beginning to dip their toes in the billing space. If you put monitoring and provisioning aside, your list really comes down to subscriber management and billing. There are some really interesting companies that solve these problems that haven&#8217;t really been considered PaaS players to date. Some have been doing this for some time like <a href="http://www.ipapplications.com" rel="nofollow">IP Applications</a> and Aria while others like <a href="http://www.zuora.com" rel="nofollow">Zuora</a> are startups generating a fair bit of buzz. I think we&#8217;re going to see a bit of consolidation here as the big PaaS players realize the scope of the operations problem they need to solve to really provide value&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

