Author: madhura
Date: Tue May 20 10:34:35 2014
New Revision: 1596187
URL: http://svn.apache.org/r1596187
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=1596187&r1=1596186&r2=1596187&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 10:34:35 2014
@@ -38,12 +38,14 @@ Notice: Licensed to the Apache Softwa
<h2>Why is this architecture so important?</h2>
<p>Cartridge model provide run time extendability to bring any type of
cartridges such as language cartridge, framework cartridge, data cartridge
..etc without binding to any specific Operating Systems. This bring polyglot
nature for tha PaaS and its is so important, because not to trap with
limitation that many PaaS offering has.</p>
<p>Another key advantage of Apache Stratos cartridge model is that it enables
to bring even legacy containers and applications into cloud with ease. So, with
Apache Stratos, you can cloud enable both existing IT assets as well as the
future IT assets that you plan to use or yet to acquire.</p>
+<img src="/images/v3/digram2.jpg"/>
<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>
<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>
+<img src="/images/v3/digram3.jpg"/>
<h3>Predicting future loads</h3>
<p>Another important capability of Apache Stratos is predicting immediate
future load, based on current health statistics. All cartridges, Load balances,
health monitors are publishing health status into CEP (Complex Event Processor)
via real time event bus. CEP will aggregate all these events and calculate
first derivative, second derivative for a given time window frame and paas
resulting streams to Auto scaler via reliable message bus.</p>
<p>Auto Scaler used motion equation to get immediate (next minute) future
load.</p>
@@ -65,6 +67,7 @@ Notice: Licensed to the Apache Softwa
<p>Provisioning - Load balancers can spin up dynamically. Based on load
balancer as cartridges, Apache Stratos will spin up defined minimum load
balancers when the first application subscription comes. Also capable of
defining load balancers to spin up in every cloud, regions enabling effective
multi-cloud deployment specially for geo-graphical based application
deployments.</p>
<p>Flexibility - Can defined service level dedicate load balancing. Easy to
define service level load balancers via REST API while capable of doing load
balancing multiple services in single load balancer.</p>
<p>Expandability - Capability of integrate any third party load balancers.
With the message broker and topology based model, its easy to integrate load
balancers like HAProxy, nginx, AWS ELB ..etc. it gives optimize load balancing
based on the deployment. (e.g use AWS ELB on EC2 deployment)</p>
+<img src="/images/v3/digram4.jpg"/>
<h2>Capability of controlling IaaS resources</h2>
<p>Different IaaS vendors provide different resource pooling, like regions,
availability zones, hosts, subnets etc. If we could not controlled these
resources and utilized in PaaS layer , leads to waist many resources. Also it
is very important controlling them to do high available kind of deployments.</p>
<p>Apache Stratos has carefully designed to address above problem. Apache
Stratos has introduced partitions, network partitions to group IaaS resources
to deploy cartridges in very controlled manner.</p>
