You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stratos.apache.org by bu...@apache.org on 2014/05/20 11:08:59 UTC

svn commit: r909380 - in /websites/staging/stratos/trunk/content: ./ about/why-apache-stratos.html

Author: buildbot
Date: Tue May 20 09:08:59 2014
New Revision: 909380

Log:
Staging update by buildbot for stratos

Modified:
    websites/staging/stratos/trunk/content/   (props changed)
    websites/staging/stratos/trunk/content/about/why-apache-stratos.html

Propchange: websites/staging/stratos/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 20 09:08:59 2014
@@ -1 +1 @@
-1596155
+1596156

Modified: websites/staging/stratos/trunk/content/about/why-apache-stratos.html
==============================================================================
--- websites/staging/stratos/trunk/content/about/why-apache-stratos.html (original)
+++ websites/staging/stratos/trunk/content/about/why-apache-stratos.html Tue May 20 09:08:59 2014
@@ -149,6 +149,7 @@
 <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>
         	</article>
     	</section>
   	</div>