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

[bu...@apache.org]

Author: buildbot
Date: Fri May 30 08:08:43 2014
New Revision: 910501

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 08:08:43 2014
@@ -1 +1 @@
-1598482
+1598486

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 08:08:43 2014
@@ -113,62 +113,7 @@
     <div id="main" role="main" class="container">
     	<section id="content" class="row">
         	<article class="span12">
-          		<h1>Why Apache Stratos is the Preferred Choice in the PaaS Space</h1>
-
-<p>Apache Stratos is a highly-extensible PaaS framework that helps to run Apache Tomcat, PHP, and MySQL applications, and can be extended to support many more environments on all major cloud infrastructures. For developers, Stratos provides a cloud-based environment for developing, testing, and running scalable applications. IT providers benefit from high utilization rates, automated resource management, and platform-wide insights, including monitoring and billing</p>
-
-<p>If you're exploring a PaaS offering to scale your business, your evaluation needs to be carried out carefully given that there are many PaaS offerings in the market</p>
-
-<h2>Important factors that need to be considered</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>Apache Stratos is the only open community controlled open-source PaaS offering. The Apache community is based on participation and meritocracy instead of financial sponsorship. In the 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. The Apache Software Foundation was established in 1999; the all-volunteer Foundation oversees more than 170 leading open source projects, including Apache HTTP Server, which is the world's most popular Web server software, Tomcat server, Cassandra, CouchDB, CloudStack, and many others.</p>
-
-<h2>Open extensible architecture</h2>
-
-<p><img src="/images/v3/digram1.jpg"/>
-<p s>Figure 1</p>
-<p>Figure 1 illustrtates how Apache Stratos' core components (Cloud Controller, CEP, Auto Scaler, and Stratos Manager, which include Artifact Distribution Coordinator and Rest API) integrate with the IaaS layer, foundation services, and dynamic services, which include cartridges.</p>
-<h2>Why is this architecture so important?</h2>
-<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>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; font-size:40px; display:inline-block;">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 scaling leads to maximized resource utilization while enabling ease in capacity planning. Moreover, it's capable of dynamic resource provisioning across multiple clouds. This provides devOps with easy and very accurate capacity planning.</p>
-<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. Yet, this is not scalable for a large deployment scenario that has hundreds, thousands, or millions of tenants.</p>
-<p>Apache Stratos has both container and in-container multi-tenancy capability, making Apache Stratos unique in the PaaS space. With in-container multi-tenancy support, users can have high tenance density, which optimizes resource utilisation by sharing resources, such as CPU and memory across tenants.</p></p>
+          		
         	</article>
     	</section>
   	</div>