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

[ma...@apache.org]

Author: madhura
Date: Fri May 30 06:43:56 2014
New Revision: 1598466

URL: http://svn.apache.org/r1598466
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=1598466&r1=1598465&r2=1598466&view=diff
==============================================================================
--- incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext (original)
+++ incubator/stratos/site/trunk/content/about/why-apache-stratos.mdtext Fri May 30 06:43:56 2014
@@ -40,9 +40,19 @@ Notice:    Licensed to the Apache Softwa
 <p><strong>The cartridge model</strong> provides run-time extendability to any type of cartridge, such as language cartridge, framework cartridge, and data cartridge without having to bind with any specific operating systems. This enables the PaaS to be of a polyglot nature, which is important, so it would not have limitations like with many other PaaS offerings.</p>
 <p>Another key advantage of the Apache Stratos cartridge model is that it enables to bring even legacy containers and applications into the cloud with ease. Therefore, with Apache Stratos, you can cloud enable both existing IT assets as well as future IT assets that you plan to use or are yet to acquire.</p>
 <img src="/images/v3/digram2.jpg"/>
-<p style="text-align: center;">Figure 2</p>
+<p>Figure 2</p>
 <p>Another important architecture design in Apache Stratos is unified communication among all components that use the message bus and real-time event bus. It provides a unified interface to integrate with any third-party system or extends to work with existing systems. Moreover, it has been carefully designed to meet heavy traffic via the real-time event bus (via thrift protocol) and uses AMQP for messages that need reliable delivery.</p>
 <p>A key extensibility aspect of Apache Stratos is its ability to plugin any IaaS due to the use of apache jclouds API. This provides more freedom to choose your own IaaS vendor, and allows to extend multiple IaaS integrations, which are important in features like cloud bursting, etc.</p>
+<h2>True flexibility for custom services</h2>
+<p>True flexibility for your own custom service is sparse in current PaaS offerings. In most cases, you have to make-do with what's available and work your solution around it. However, with the Apache Stratos cartridge model, you can create a custom service without having to deal with any limitations or boundaries. Your cartridge can be fully configured (installed all software, configuration, etc.) or zero configured (enable cartridge user to install and configure what they want) or something in-between. This will allow you to customize your PaaS to be in sync with your current business workflows.</p>
+<a class="cBookmark" name="multi-factored-auto-scaling"/></a>
+<h2>Multi-factored auto scaling</h2>
+<p>A majority of PaaS providers only used HTTP traffic to auto scale or for dynamic resource provisioning. It comes with limitations on scaling non-HTTP-based applications. However, Apache Stratos auto scaler can takes HTTP traffic and non-HTTP health data to carry out intelligent dynamic resource provisioning. Further, it's capable of dealing with these multiple factors and run through scaling algorithm simultaneously. Inflight request count on load balancers and load average; memory consumption are some of these factors and it's easy to extend (benefit from clean unified communication) to any factors that are required to take care of auto scaling.</p>
+<img src="/images/v3/digram3.jpg"/>
+<h2>Predicting future loads</h2>
+<p>Another important capability of Apache Stratos is predicting immediate future load based on current health statistics. All cartridges, load balancers, and health monitors publish health status into CEP (complex event processor) via a real-time event bus. The CEP will aggregate all of these events and calculate the first derivative and second derivative for a given timeframe and paas the resulting streams to the auto scaler via the reliable message bus.</p>
+<p>The auto scaler uses motion equation to get the immediate (next minute) future load.</p>
+<span style="padding: 40px;">s = ut+ 1/2 at<sup>2</sup></span>
 
 
      
\ No newline at end of file