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

[bu...@apache.org]

Author: buildbot
Date: Fri May 30 05:19:20 2014
New Revision: 910482

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 Fri May 30 05:19:20 2014
@@ -1 +1 @@
-1597720
+1598458

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 Fri May 30 05:19:20 2014
@@ -113,82 +113,7 @@
     <div id="main" role="main" class="container">
     	<section id="content" class="row">
         	<article class="span12">
-          		<h1>Why Apache Stratos Stand Out Among Other PaaS Vendors</h1>
-
-<p>If your business is looking PaaS offering to scale your business, your evaluation need to be carefully carry out since there are many PaaS offering are in the market. In this article I will discuss some important factors, that need to be consider before choosing suitable PaaS vendor and also discuss why Apache Stratos stand out among other PaaS vendors.</p>
-
-<h2>Important factors that need to be consider</h2>
-
-<ul>
-<li>True community ecosystem</li>
-<li>Open extensible architecture</li>
-<li>True flexibility for custom services</li>
-<li>Multi-factored auto scaling</li>
-<li>Multi-tenancy</li>
-<li>Scalable dynamic load balancing</li>
-<li>Capability of controlling IaaS resources</li>
-<li>Logging, metering and monitoring</li>
-<li>Cloud bursting</li>
-</ul>
-
-<h2>True community ecosystem</h2>
-
-<p>If you evaluate current PaaS vendors, one of major misleading facts that you can see that they claim their offering is driven by the community. But if you carefully analyzed, these offerings either belong to a single corporation or a few select large sponsors. But Apache Stratos is the only open community controlled open-source PaaS offering. Apache community, where participation is based on participation and meritocracy instead of financial sponsorship. Apache community meritocratic process known as "The Apache Way," more than 400 individual members and 3,500 committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide. Apache Software Foundation is established in 1999, the all-volunteer Foundation oversees more than one hundred and seventy leading Open Source projects, including Apache HTTP Server --the world's most popular Web server software, Tomcat server, Cassandra, CouchDB, CloudStack and many others.</p>
-
-<p>This is very important that, if you think your PaaS offering need to have true community ecosystem, find out carefully how established and has openness of the saying community.</p>
-
-<h2>Open extensible architecture</h2>
-
-<p><img src="/images/v3/digram1.jpg"/>
-<p>Above diagram shows, how Apache Stratos core components (Cloud Controller, CEP, Auto Scaler, Stratos Manager which include Artifact distribution Controller and Rest API) integration with IaaS layer, foundation services and dynamic services that are cartridges.</p>
-<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>
-<a class="cBookmark" name="multi-factored-auto-scaling"/></a>
-<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>
-<span>s = ut+ 1/2 at<sup>2</sup></span>
-<ul class="cEcation">
-<li>s = predicted load</li>
-<li>u = first derivative (eg. first derivative of current load average)</li>
-<li>t = time interval (eg. one minute)</li>
-<li>a = second derivative (eg. second derivative of current load average)</li>
-</ul>
-<P>Multi factored auto scaler leads to maximize resource utilization while benefiting easy of capacity planning. Also its capable of dynamic resource provisioning across multiple clouds. This give devOps life 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. But this is not scalable for large deployment scenario which has hundred thousand or million of tenants.</p>
-<p>Apache Stratos has both container and in-container multi-tenancy capability provide Apache Stratos to be in uniqueness in the PaaS space. With the In-container multi-tenancy support user can have high tenance density which optimised resource utilisation by sharing resources such as CPU and memory across the tenants.</p>
-<a class="cBookmark" name="scalable-dynamic-load-balancing"/></a><h2>Scalable dynamic load balancing</h2>
-<p>Load balancers play a major role in scaling application in the cloud. Load balancers distribute incoming traffics into several server nodes, or clusters, or other resources to maximize the throughput, minimise response time and provide mechanism scale application based on the workload.</p>
-<p>Apache Stratos capable of provision scalable load balancers for any IaaS clouds well as integrate any third party load balancers. This gives more flexibility and extendability while providing more efficient load balancing based on deployment environment.</p>
-<h3>Apache Stratos Load Balancing features and benefits</h3>
-<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>
-<h3>Partitions</h3>
-<p>Partitions are logical group, that can defined by devOps based on available IaaS resource pooling like regions, availability zones ..etc.  With this definitions, Apache Stratos capable of selecting where to spawn Cartridge instances, selected resource pool which is very useful in deployment like high available or disaster recovery.</p>
-<h3>Network Partitions</h3>
-<p>With this concept, Apache Stratos can logically group one or more partitions that are reside in same network.  With this network partition concept, Apache Stratos Auto Scaler can have intelligence of monitor and predict load of particular network bound regions and take necessary auto scaling decisions very easily. This also very unique and important feature Apache Stratos bringing into PaaS world.</p>
-<p>Smart Policies</p>
-<p>With the partitions and Network partitions, devOps can defined smart policies namely auto scaling and deployment policies, which can be used in cartridge subscriptions. Smart policies will provide cloud SLAs which absolutely mandatory when you consider cloud solutions.</p>
-<h2>Logging, metering and monitoring</h2>
-<p>Logging, metering and monitoring are primary but important features you should not neglect. Apache Stratos capable of capturing all health statistics, application logs well as usage and aggregate them into centralized location. it provide devOps life easy otherwise it is impossible task to login and monitor each and every instances in a large scale deployment which has hundreds of instances.</p>
-<a class="cBookmark" name="cloud-bursting"/></a><h2>Cloud bursting</h2>
-<p>Cloud bursting is now widely discuss since it reduces TCO (Total Cost of Ownership) while provisioning application into another cloud to handle peak load. Like all other aspect, Apache Stratos cloud bursting also carefully design to work with private, public and hybrid cloud with effective provisioning load balancers per bursting cloud.</p></p>
+          		
         	</article>
     	</section>
   	</div>