svn commit: r1596160 - /incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext

[ma...@apache.org]

Author: madhura
Date: Tue May 20 09:18:35 2014
New Revision: 1596160

URL: http://svn.apache.org/r1596160
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=1596160&r1=1596159&r2=1596160&view=diff
==============================================================================
--- incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext (original)
+++ incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext Tue May 20 09:18:35 2014
@@ -40,8 +40,7 @@ Notice:    Licensed to the Apache Softwa
 <p>Another important architecture design in Apache Stratos is unified communication among all components using message bus and real time event bus. It provide unified interface to integrate with any third party systems or extending to work with existing systems. Also its carefully design to cater heavy traffic via real time event bus (via thrift protocol) and used AMQP for messages which need reliable delivery.</p>
 <p>Another important extendability of Apache Stratos is that ability to plugin any IaaS due to the use of apache jclouds API. Which give more freedom to choose your own IaaS vendor, and it also enable to extend multiple IaaS integration, which is important in features like cloud bursting etc.
 <h2>True flexibility for custom services</h2>
-<p>If you look at current PaaS offering, you can't get true flexibility for your own custom service. Many cases, you have to bare with what they are offering and make your solution around it.  With the Apache Stratos cartridge model, you can create custom service, without any limited boundaries. Your cartridge can be fully configured (installed all software, configuration ..etc) or zero configured ( let cartridge user to install and config what they want) or in-between.  This will allow you to customise your PaaS to suite in your current business workflows.</p>
-<p>If you look at current PaaS offering, you can’t get true flexibility for your own c
+<p>If you look at current PaaS offering, you can't get true flexibility for your own custom service. Many cases, you have to bare with what they are offering and make your solution around it.  With the Apache Stratos cartridge model, you can create custom service, without any limited boundaries. Your cartridge can be fully configured (installed all software, configuration ..etc) or zero configured (let cartridge user to install and config what they want) or in-between.  This will allow you to customise your PaaS to suite in your current business workflows.</p>
 <h2>Multi-factored auto scaling</h2>
 <p>Majority of PaaS providers only used http traffic to auto scale or dynamic resource provisioning. It gives limitation on scaling non-http based application. But Apache Stratos auto scaler can take http traffic and non-http health data to do intelligent dynamic resource provisioning. Also its capable of dealing with these multiple factors run through scaling algorithm simultaneously. Inflight request count on Load Balancers, Load average, Memory consumption are some of factors and its easy to extend (benefit from clean unified communication) to any factors need to take care of the auto scaling.</p>
 <h2>Predicting future loads</h2>