Author: madhura
Date: Sat May 31 02:41:52 2014
New Revision: 1598795
URL: http://svn.apache.org/r1598795
Log: (empty)
Modified:
incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext
Modified: incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext?rev=1598795&r1=1598794&r2=1598795&view=diff
==============================================================================
--- incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext
(original)
+++ incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext Sat
May 31 02:41:52 2014
@@ -60,6 +60,7 @@ Notice: Licensed to the Apache Softwa
<li>a = second derivative (eg. second derivative of current load average)</li>
</ul>
<p>Multi factored auto scaling leads to maximized resource utilization while
enabling ease in capacity planning. Moreover, it's capable of dynamic resource
provisioning across multiple clouds. This provides devOps with easy and very
accurate capacity planning.</p>
+<a class="cBookmark" name="multi-tenancy"/></a>
<h2>Multi-tenancy</h2>
<p>Multi-tenancy has different levels of isolations. Almost all PaaS vendors
only provide container multi-tenancy like virtual machine, LXC or docker, etc.
Yet, this is not scalable for a large deployment scenario that has hundreds,
thousands, or millions of tenants.</p>
<p>Apache Stratos has both container and in-container multi-tenancy
capability, making Apache Stratos unique in the PaaS space. With in-container
multi-tenancy support, users can have high tenance density, which optimizes
resource utilisation by sharing resources, such as CPU and memory across
tenants.</p>
