WSO2 Cloud Middleware

2,605 views
2,397 views

Published on

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Do you know if Carbon stack is as per the definition of cloud middleware defined at http://www.pavan-pendyala.co.cc/news/cloudmiddleware? Also, id there carbon middleware hosted on the public cloud for developers to use?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
2,605
On SlideShare
0
From Embeds
0
Number of Embeds
230
Actions
Shares
0
Downloads
90
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

WSO2 Cloud Middleware

  1. 1. WSO2 Cloud Middleware Afkham Azeez Software Architect & Product Manager, WSO2 WSAS
  2. 2. Overview ● Multitenancy ● Autoscaling ● Cloud middleware platform
  3. 3. 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
  4. 4. 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
  5. 5. 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
  6. 6. An Example: Multitenant Service Deployment & Dispatching
  7. 7. 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
  8. 8. 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
  9. 9. Deploying a Service on the Cloud AMI Instances 9
  10. 10. Deploying a Service on the Cloud 10
  11. 11. Deploying a Service on the Cloud 11
  12. 12. Deploying a Service on the Cloud Service is available now 12
  13. 13. Autoscaling – Steady load 13
  14. 14. Autoscaling – Load increasing Load Increases 14
  15. 15. Autoscaling – Load increasing Startup new instances 15
  16. 16. Autoscaling – Steady load New instances join group 16
  17. 17. Autoscaling – Load decreasing Load Decreases 17
  18. 18. Autoscaling – Load decreasing Terminate instances 18
  19. 19. Autoscaling – Steady load 19
  20. 20. Deployment Architecture 20
  21. 21. Analysis & Results 21
  22. 22. Analysis & Results 22
  23. 23. 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
  24. 24. WSO2 Cloud Middleware Platform 24
  25. 25. 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
  26. 26. Service Firewall Pattern
  27. 27. Secure Data Pattern Example from Financial Domain  Secure/private Data = Client Portfolios  Public Data = Market Data
  28. 28. Cloud Identity – Identity As A Service
  29. 29. 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
  30. 30. Questions
  31. 31. Thank You!

×