<?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: A Case for Private PaaS</title>
	<atom:link href="http://www.janakiramm.net/blog/a-case-for-private-paas/feed" rel="self" type="application/rss+xml" />
	<link>http://www.janakiramm.net/blog/a-case-for-private-paas</link>
	<description>Cloud Specialist</description>
	<lastBuildDate>Mon, 16 Jan 2012 13:46:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Govind</title>
		<link>http://www.janakiramm.net/blog/a-case-for-private-paas#comment-67</link>
		<dc:creator>Govind</dc:creator>
		<pubDate>Sun, 29 Aug 2010 04:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.janakiramm.net/?p=2462#comment-67</guid>
		<description>Honestly Jani - Private PaaS - when it becomes reality should abstract out PaaS itself. My application is there - manage provisioning/security/integration. There should not be need to learn PaaS concept at all.  
There is huge existing repository of applications and their hardware - if it can be utilized and managed - much better.  BTW multi-tenancy is something one needs to think about with or without PaaS etc.  It was there in ASP (no not microsoft asp) days and anybody who has created hosted platform knows about perils of too much abstraction..
Private PaaS focus should be enabling existing apps to not worry about PaaS. If they do - they will face friction, because returns are too low. That is why it is restricted release to test the waters.  
One can always work with virtualization vendors to abstract out the metal/os and just run the app.  
Here too vendors who provide ability to run diverse set of applications/workloads will succeed the farthest. 
</description>
		<content:encoded><![CDATA[<p>Honestly Jani &#8211; Private PaaS &#8211; when it becomes reality should abstract out PaaS itself. My application is there &#8211; manage provisioning/security/integration. There should not be need to learn PaaS concept at all.<br />
There is huge existing repository of applications and their hardware &#8211; if it can be utilized and managed &#8211; much better.  BTW multi-tenancy is something one needs to think about with or without PaaS etc.  It was there in ASP (no not microsoft asp) days and anybody who has created hosted platform knows about perils of too much abstraction..<br />
Private PaaS focus should be enabling existing apps to not worry about PaaS. If they do &#8211; they will face friction, because returns are too low. That is why it is restricted release to test the waters.<br />
One can always work with virtualization vendors to abstract out the metal/os and just run the app.<br />
Here too vendors who provide ability to run diverse set of applications/workloads will succeed the farthest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jani</title>
		<link>http://www.janakiramm.net/blog/a-case-for-private-paas#comment-65</link>
		<dc:creator>Jani</dc:creator>
		<pubDate>Thu, 26 Aug 2010 18:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.janakiramm.net/?p=2462#comment-65</guid>
		<description>Slightly disagree. Private PaaS is mostly managed by the vendors who
provided it. It is far more easier to manage and maintain than IaaS.</description>
		<content:encoded><![CDATA[<p>Slightly disagree. Private PaaS is mostly managed by the vendors who<br />
provided it. It is far more easier to manage and maintain than IaaS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan Suero</title>
		<link>http://www.janakiramm.net/blog/a-case-for-private-paas#comment-63</link>
		<dc:creator>Juan Suero</dc:creator>
		<pubDate>Thu, 26 Aug 2010 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.janakiramm.net/?p=2462#comment-63</guid>
		<description>dude private PAAS is SOA ontop of private IAAS</description>
		<content:encoded><![CDATA[<p>dude private PAAS is SOA ontop of private IAAS</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten Visser</title>
		<link>http://www.janakiramm.net/blog/a-case-for-private-paas#comment-44</link>
		<dc:creator>Maarten Visser</dc:creator>
		<pubDate>Fri, 30 Jul 2010 15:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.janakiramm.net/?p=2462#comment-44</guid>
		<description>The potential for Private PaaS is indeed huge! Private PaaS is THE answer to all those organizations who like the bennefits of a Cloud OS, but are scared about privacy and security...</description>
		<content:encoded><![CDATA[<p>The potential for Private PaaS is indeed huge! Private PaaS is THE answer to all those organizations who like the bennefits of a Cloud OS, but are scared about privacy and security&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

