WSO2 Cloud Middleware
Upcoming SlideShare
Loading in...5

WSO2 Cloud Middleware






Total Views
Views on SlideShare
Embed Views



6 Embeds 219 108 96 11 2 1 1



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
  • Do you know if Carbon stack is as per the definition of cloud middleware defined at Also, id there carbon middleware hosted on the public cloud for developers to use?
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

WSO2 Cloud Middleware WSO2 Cloud Middleware Presentation Transcript

  • WSO2 Cloud Middleware Afkham Azeez Software Architect & Product Manager, WSO2 WSAS
  • Overview ● Multitenancy ● Autoscaling ● Cloud middleware platform
  • Mission ● WSO2 aims to provide the best complete Enterprise Software Platform: – for Cloud – to be used in EC2, Azure, VMware, Private Cloud, etc – in the Cloud – available to use in WSO2’s managed cloud – across the Cloud – bridging public and private clouds and – under the Cloud – providing essential infrastructure to manage cloud systems
  • Multitenancy ● A single instance of the software runs on a server, serving multiple client organizations (tenants). ● Different from multi-instance architecture where separate software instances (or hardware systems) are set up for different tenants. ● A software application is designed to virtually partition its data and configuration so that each tenant works with a customized virtual application instance. ● Total data & business logic isolation is a fundamental requirement
  • Multitenancy - Advantages ● All advantages of *aaS – Automatic upgrades, bug fixes including security fixes – No infrastructure maintenance cost – HA & scalability – Overall cost saving ● For the service provider: Cost of software & hardware amortized over many customers ● For the tenant: Small initial cost & monthly or usage based payment
  • An Example: Multitenant Service Deployment & Dispatching
  • Autoscaling ● The Problem – Fault tolerance, high availability & scalability are essential prerequisites for any enterprise application deployment – High cost associated with achieving high availability & scalability. – System throughput should not degrade under load
  • Autoscaling ● The Solution – Traditional solution ● Buying safety-net capacity – Better solution ● Scale-up the system when the load increases ● Scale-down the system when the load decreases ● Should not have idling nodes ● Pay only for the actual computing power & bandwidth utilized ● Cloud independent autoscaling
  • Deploying a Service on the Cloud AMI Instances 9
  • Deploying a Service on the Cloud 10
  • Deploying a Service on the Cloud 11
  • Deploying a Service on the Cloud Service is available now 12
  • Autoscaling – Steady load 13
  • Autoscaling – Load increasing Load Increases 14
  • Autoscaling – Load increasing Startup new instances 15
  • Autoscaling – Steady load New instances join group 16
  • Autoscaling – Load decreasing Load Decreases 17
  • Autoscaling – Load decreasing Terminate instances 18
  • Autoscaling – Steady load 19
  • Deployment Architecture 20
  • Analysis & Results 21
  • Analysis & Results 22
  • WSO2 Cloud Middleware Platform ● Multitenant enabled middleware technology that to support the WSO2 SOA Platform. ● A combination of the following middleware aspects: – Data management – Identity/security management – Service hosting, mediation and management – User interfaces and portals – Billing and metering – Management and monitoring
  • WSO2 Cloud Middleware Platform 24
  • WSO2 Cloud Middleware Platform – Use cases ● Exposing internal services securely on the cloud ● Centralized management, control & monitoring of services using Cloud ESB ● Securely exposing data on the cloud using Cloud Data Services – Mashing up content & secure data, and providing a dashboard ● Centralized governance on the cloud ● Centralized identity management on the cloud 25
  • Service Firewall Pattern
  • Secure Data Pattern Example from Financial Domain  Secure/private Data = Client Portfolios  Public Data = Market Data
  • Cloud Identity – Identity As A Service
  • WSO2 Cloud Middleware Platform – Advantages ● Centralized management, backup ● Gradually build up the services portfolio ● Usage based payment ● Autoscaling in the cloud ● Readily available infrastructure ● No setup cost & hassle ● Ability to bridge from internal data center to the cloud ● Ability to scale-out to the cloud, on demand 29
  • Questions
  • Thank You!