WSO2Con Asia 2014 - Essential Elements of an Enterprise PaaS


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

WSO2Con Asia 2014 - Essential Elements of an Enterprise PaaS

  1. 1. Essential Elements of an Enterprise PaaS Lakmal Warusawithana Committer and PPMC member, Apache Stratos (Incubating) Software Architect WSO2 Inc
  2. 2. What are Essentials ? Why Important? • Open extensible architecture • Intelligent capacity on demand • Scalable and dynamic load balancing • Multi-tenancy • Multi cloud and cloud bursting • Logging, Metering and Monitoring • Multi provider echo system • Efficiency and security • Controlling IaaS resources
  3. 3. Open Extensible Architecture
  4. 4. Open Extensible Architecture… Why Stratos architecture so important? • Cartridge model enable bringing in even legacy apps into cloud • Unified communication across components in the PaaS using message broker • Centralized monitoring and metering with unified logging framework • Ability to plugin any IaaS due to the use of jclouds API • Ability to plugin any third party load balancer using message broker model • Ability to plugin any third party health checking/monitoring framework
  5. 5. Intelligent Capacity On Demand How is it working? • Scaling algorithm can use multiple factors. - Load average of the instance - Memory consumption of the instance - In-flight request count in LB • Capable of predicting future load - Real time analysis of current load status using CEP integration - Predict immediate future load based on CEP resulting streams
  6. 6. Intelligent Capacity On Demand… Why should one care? • Maximize resource utilization • Easy to do capacity planning • Dynamic load based resource provisioning • Optimizing across multiple clouds What are the advantages? • Make DevOps life easy • More accurate capacity planning !
  7. 7. Scalable and Dynamic Load Balancing How Scalable it is? • In theory infinite - horizontal scaling - limited by resource (instance capacity) availability How Dynamic it is? • Load Balancers are spawned dynamically - LB too is a cartridge • In case of multi-cloud, multi-region, LB can scale per cloud/region • Per service cluster LB
  8. 8. Scalable and Dynamic Load Balancing… What is unique about Stratos? • Cartridge based LB model • Can bring any third-party LB - As easy as plugging into LB extension API - HAProxy, nginx, AWS ELB ! !
  9. 9. Multi-tenancy What MT model does Stratos support? • Container MT - virtual Machine, LXC, Docker • In-container MT - within VM/LXC/Docker tenancy What are the advantage of this model? • Optimizing resource utilization - by sharing resource such as CPU, memory across tenants - low footprint, based on utilization/usage of the tenants app • No need dedicated resource allocation for tenants
  10. 10. Logging, Metering and Monitoring What captured? • Instance up/down time • Each and every instances health status - application health, load average, memory consumption • Application logs What are the advantages? • DevOps life easy - centralize log viewer - centralize dashboard • Easy to throttling
  11. 11. Cloud Bursting What is it? • Expanding/provisioning application into another cloud to handle peak load. Why Should one care? • Resource peak time can be off-loaded to third party clouds/ resources What is unique about Stratos? • Can off-load to any cloud - Private, Public and Hybrid • Easy to managed with the model of LB per busting cloud
  12. 12. Cloud Bursting… What are the advantages? • Make DevOps life easy • Low TCO, and higher utilization existing dedicated resources ! ! ! !
  13. 13. Thank you!