Cloud Native PaaS Advantage

Cloud Native PaaS Advantage






Total Views
Views on SlideShare
Embed Views



1 Embed 28 28



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Cloud Native PaaS Advantage Cloud Native PaaS Advantage Presentation Transcript

    • Cloud-Native PaaS Advantage
    • Cloud-­‐Na)ve  PaaS  Accelerates  Connected  Business
    •  Placing  PaaS  in  a  Connected  Business  Context   Reduces   interac)on   fric)on  and  cost     Accelerates   interac)ons   inside  and   outside  the   organiza)on     Increases   engagement  and   enhances   produc)vity           Senses     business  ac)vity   and     automa)cally   adapts
    • Mapping  The  PaaS  Promise   On-­‐demand     Internet  Accessible   Self  Service   Cloud  Services     Resource     Pooling     Measured  service   Measured  Service     DevOps         Elas)c   Scalability    
    • PaaS Blockers •  Only suitable for web applications •  Fuzzy cost model benefits •  Dynamic environment introduces management complexity •  High learning curve to adopt new practices •  Gaining Development and Operations Buy-in
    • Technology Trends Shaping PaaS •  Rise in cloud based DevOps and ALM adaptation •  Rise in demand for hybrid cloud configurations •  Big data analysis and complex event processing in the cloud •  Greater emphasis on required change management and cost benefits when enterprise organizations select aPaaS instead of CEAP
    • Baseline Transformation Pre-requisites
    • WSO2  xPaaS  -­‐  Key  Differen)ators   •  A complete set of Cloud-Native middleware services enabling complex project delivery •  Enterprise-ready foundation •  Re-shapes team collaboration and reduces wait states •  Business driven PaaS –  Lowest run-time cost –  CxO dashboards delivering portfolio visibility –  Development and DevOps dashboards Showback/chargeback billing
    • WSO2 Architecture Advantage Availability Scalability Management Load monitor Tenant partitioning Private jet mode Cloud controller Balancing and failover across hybrid clouds Ghost deployment BigData Logging infrastructure State replication and session replication BAM 2.0 architecture Artifact Distribution Controller and Deployment synchronization Multiple load balancers with keepalived or DNS RR Auto-scaling P2 Repository Native multi-tenancy Elastic Load Balancer Consistent management and infrastructure services across entire platform Dynamic Clustering Multi-tenant shared container Management console
    • WSO2 Cloud Native Advantage •  Automated governance •  Multi-tenant •  On-demand •  Elastic platform self service scalability •  Service-aware •  Cartridge •  DevOps load balancing extensions tooling
    • Multi-tenancy
    • Enhance Virtualization models Agility Stratos Carbon (Shared Process) Stratos Cartridge (LXC) Virtual Machine Pure Hardware Resource Optimization WSO2 Private PaaS supports all models and model combinations
    • Elastic Scalability Tenant-aware and Service-Aware Load Balancing
    • Container Tenancy Implications •  Traditional application servers can host multiple applications, but resource isolation limitations may restrict sharing •  •  Common limitations: code deployment, security, administration Implication •  •  •  •  1 application server per tenant (N) application server license per (N) tenants (N) IaaS node per (N) tenant Multi-tenant application servers can host multiple tenant applications with appropriate resource isolation •  Limitations overcome by: •  •  •  OSGI class loading, custom security manager, Cloud aware code deployer, tenant-aware administration screens 1 application server per N (~7-100) tenants 1 application server license per N tenants
    • Partitioning and Tenancy Implications Five (5) Container Instances Tenant Traffic Application Solution Tenant Partition Tenant-1 Tenant-2 Tenant-3 Container AS-1 ESB-1 AS-2 ESB-2 ESB-3 Tenant Context Tenant-1 Tenant-1 Tenant-2 Tenant-2 Tenant-3
    • Partitioning and Tenancy Implications Three (3) Container Instances Tenant Traffic Application Solution Service Partition Container Tenant Context Web Application ESB ESB-1 Tenant-1 ESB-2 Tenant-3 Tenant-2 AS-1 Tenant-1 Tenant-2
    • Cloud-Native Log Service
    • WSO2 PaaS Architecture
    • Understanding the Stratos Controller The Stratos Controller is a set of components that deploy, scale, monitor, and manage an elastic middleware Cloud. •  Cloud Controller: using jclouds creates/removes VM or LXC instances, based on input from - •  Load Monitor: acquires load information from multiple sources •  Elastic Load Balancer: distributes requests to the correct instances, based on tenant and load balance, including rewriting URLs •  Artifact Distribution Server: takes complete applications and breaks into perinstance components, which are then loaded into instances by •  Deployment Synchronizer: checks out the right code for an instance •  Management Console: allows control of all this by either Web UI or commandline tooling
    • Stratos Core Services •  The Stratos Core Services provide essential capabilities to Cartridges and applications running in Stratos (all available “as-a-Service”) Logging (Log4J, Syslog) •  Data (MySQL and Cassandra) •  Identity (SAML2, OAuth, OpenID, XACML) •  Registry/Repository (for metadata and config) •  Billing and Metering •  Monitoring (BAM) •  File System (HDFS) • 
    • Artifact Distribution Controller
    • Understanding Cartridges •  A cartridge is a package of code/ configuration that plugs into Stratos to offer a new PaaS Service •  e.g. Carbon ESB cartridge plugs in to provide a Stratos ESB-as-a-Service •  PHP Cartridge plugs in to provide PHP-as-aService •  A cartridge is a VM image plus config •  In •  Stratos 2.0 you need a VM per IaaS e.g. need to create both EC2 and LXC image to use on both IaaS
    • Cartridge Tenancy •  A •  cartridge can operate in two modes: Single tenant •  •  •  Stratos will run and manage a separate instance for each tenant The PHP Cartridge runs this way Multi-tenant •  •  •  Stratos will run multiple instances partitioned so that sets of tenants run on sets of instances Each instance of a Cartridge may run more than one tenant Carbon Cartridges run this way
    • WSO2 DevOps Advantage •  Complete lifecycle automation Collaboration oriented •  Project workspaces and dashboards •  Continuous delivery
    • DevOps PaaS Differentiation •  Self service project and policy configuration •  Via project configuration portals •  Security, service levels, frameworks, usage, topology •  Automated platform provisioning •  Via service tier templates •  Framework and policy enforcement points (PEPs) •  Process automation •  Continuous build, test, and deployment •  Code promotion and synchronization across environments and servers •  Dependency analysis and impact analysis
    • To establish responsive Iterations Adopt Unified, Full Life Cycle DevOps
    • To Establish Responsive Iterations, increase DevOps automation
    • Shape the Cloud
    • Contact us: Follow us:!/wso2
    • Recommended Reading •  The Path to Responsive IT • responsive-it •  DevOps Meets ALM in the Cloud • in-the-cloud-cloud-devops-paas •  Cloud-Native Advantage • advantage-multi-tenant-shared-container-paas