Delivering On-Demand and Shared Middleware Services
•
0 likes•626 views
This document discusses delivering on-demand and shared middleware services through a Platform as a Service (PaaS) model. It describes how PaaS can provide services instead of servers, disrupt traditional IT topology and funding, and enable IT to operate as a business. It also discusses tenants, containers, partitioning, capacity planning, the Stratos architecture, and how PaaS can reduce total cost of ownership and increase project agility through development services. Finally, it suggests how businesses can offer their capabilities as a service through a PaaS-enabled ecosystem.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Delivering On-Demand and Shared Middleware Services
Similar to Delivering On-Demand and Shared Middleware Services (20)
More from WSO2
More from WSO2 (20)
Recently uploaded
Recently uploaded (20)
Delivering On-Demand and Shared Middleware Services
- 1. Delivering On-Demand and Shared Middleware Services Chris Haddad Asanka Abeysinghe Read more about PaaS at http://blog.cobia.net/cobiacomm Try StratosLive https://stratoslive.wso2.com/
- 2. Delivering On-Demand and Shared Middleware Services • Services instead of Servers • Disruptors ① Topology ② Project funding and investment ③ IT as a Business ④ Shared policy and automated governance ⑤ Development services ⑥ Your Business as a Service and Ecosystem Platforms
- 3. Cloud Services instead of Servers Existing IT infrastructure
- 4. Platform as a Service Architecture What is a tenant? • An isolated or personalized run-time environment context that cannot be shared across PaaS consumers • Tenant specific personalization can occur across multiple personalization dimensions • Information access privileges • Information aggregation and composition • Business processes and rules • Service levels and Quality of Service • Security policies, subscriber entitlements, and social network access privileges • Monetization rates • Personalization may require loading code, configuration files, or data • Tenant isolation dictated by expected performance, security requirements, and legacy technology. • PaaS security managers, code deployers, and tenant-aware load balancing influences required container-level isolation
- 5. Platform as a Service Architecture What is a container? • A standalone, Internet addressable node offering application platform services • Web application hosting, API management, integration endpoint hosting, ESB mediation, registry services, identity management, relational database • Containers host tenant resources and context • Code, configuration files, data, process definitions, rules, policies, entitlements • Containers may serve • a single tenant at a time (dedicated), or • multiple-tenants at a time (shared)
- 6. Partitioning and Tenancy Implications Five (5) Container Instances Tenant Application Solution Traffic 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
- 7. Partitioning and Tenancy Implications Three (3) Container Instances Tenant Application Solution Traffic Web Service Partition ESB Applicati on Container ESB-1 ESB-2 AS-1 Tenant Context Tenant-1 Tenant-3 Tenant-2 Tenant-1 Tenant-2
- 8. Cloud Application Platform Shared Middleware Services
- 9. How to size an infrastructure • Expected Maximum TPS – Any max latency requirements • Work done per transaction • Size of messages • Availability • Deployment needs (e.g. specific setup might need based on the infrastructure policy etc.)
- 10. Cloud Capacity Planning • Service types • System load – Per service type – Administration • Scaling – Static – Dynamic • PaaS system and deployment architecture • Limitation of IaaS
- 11. WSO2 Stratos Component Architecture Controller Service Cluster 1:M • Stratos Controller - Management, Governance, Monitoring component - System security • Stratos Service Cluster - Worker nodes provide the runtime for application logic / services - Administrator nodes to create, manage, govern the application logic / services
- 12. Stratos Service Cluster : Worker Node • Cloud enabled Carbon runtime to host various services - Multi-tenanted - Dynamically scaled
- 13. Scaling Worker Nodes • Front by a load-balancer • Dynamically scale horizontally by the load-balancer
- 14. Stratos Service Cluster : Admin Node • Web based management, configuration and monitoring console to create, manage and govern the Cloud services
- 15. Stratos Service Cluster : Admin Node • Read/Write node for the service cluster • Load-balancer will not route any work requests to the admin node
- 17. Stratos Controller Self Service Portal Stratos BAM Manager Data Collector System storage Stratos BAM Identity Summarizer Syslogd OS utility to manage logs (syslog format) System user management & SSO
- 18. Scaling the Stratos Controller
- 19. Formula for Static Scaling Stratos Controller i = 2 + (2 +x) y LB + Admin Node i – Number of WSO2 Carbon instances x – Number of worker nodes per service cluster y – Number of service clusters In most cases each service node will not have equal number of worker nodes. Stratos Controller instances. i = Z + (2 + x1) + (2 + x2) + …….. + (2 + xn) 2
- 20. Project Funding and Investment – Service TCO TCO sharing benefits when running ESB as a Service • Infrastructure • License • Management • Ownership • Governance ESB infrastructure immediately ready for projects
- 21. WSO2 Total Cost of Ownership Advantage • Rapid elasticity • Containers shared across multiple tenants • Capacity managed per service, not per tenant • Single, flat container partition space enables maximum sharing • Containers may be partitioned by service • Resource Pooling • Application footprint lower than single tenant, dedicated container deployment • Lazy loading further minimizes footprint
- 22. WSO2 Total Cost of Ownership Advantage • Measured Service and Pay Per Use • Cloud infrastructure investment recaptured after 4 tenants subscribe (at full-time usage per tenant) • Can meter and bill based on business transaction usage, application count • On-demand self-service • Application teams do not have to specify infrastructure topology (i.e. server count) • Subscribe to application platform services instead of application server instances
- 23. Project Funding and Investment – Service TCO Use Case 2: ESB-as-a-Service, Low Tenant Count http://wso2.com/whitepapers/cloud-native-advantage-multi-tenant-shared-container-paas/
- 24. Business APIs • Publish same API API API API • Publish same API in Tenant Tenant Tenant different forms • Customer specific PaaS policies, plans • Scale based on the IaaS customer tier • Billing and usage reports
- 25. Federated Deployment : Traditional Store Store Store Store Regional Regional Regional Regional Datacenter Datacenter Datacenter Datacenter Master Datacenter
- 26. Federation with Multitenancy • Remove the regional Store Store Store Store datacenters • Provide isolated environments for Tenant Tenant Tenant processes, policies and Super Tenant data PaaS • Shared processes, policies and data IaaS • Centrally manage and governed • Ability scale based on the demand
- 27. Increasing project agility via Development services Potential Development Services • Issue tracking • Source Code Management • Automated Software development LifeCycle Governance – approval, workflow, • Service Store, API Store • Policy definition • Code Build • Integration Test • Continuous delivery
- 28. WSO2 App Factory 6/27/2012 28
- 29. WSO2 AppFactory Partner and Mobile applications API Management Lightweight High Performance Integration Existing IT infrastructure Scalable Private Cloud infrastructure CIO/Management Workflow managed Dashboard build and deploy Governance Stratos Multi-tenant elastic and Identity integration and ESB runtime WSO2 AppFactory
- 30. Your Business as a Service and Ecosystem Platforms • Beyond APIs – because it creates a shared governance model and runtime • An opportunity to add significant value to partners: • A complete environment that they can customize • Not just the look and feel but also the behaviour • An ideal platform for shared revenue • A shift in business models enabled by cloud technology
- 31. Users Partners Beyond APIs: “Your Business As A Service” Tenant Tenant Tenant Tenant Apps Apps Apps Apps Ecosystem Owner PaaS / Stratos API Management / API Store Existing business systems as APIs
- 32. Tenant / Consumer Personalization Dimensions • Information access privileges • Information aggregation and composition • Social network access privileges • Business processes and rules • Service levels and Quality of Service • Security policies • Monetization rates
- 33. Getting Started To shift from servers to services • Size the application platform service cloud • Implement multi-tenant container sharing and reduce total cost of ownership • Build extensible, configurable applications, services, and APIs • Establish a federated architecture and institutionalize best practices with governance • Adopt development services and increase project agility • Facilitate partner extensions with WSO2 AppFactory
- 34. Resources • Try StratosLive right now: – https://stratoslive.wso2.com/ • Read about Stratos: – http://wso2.com/cloud/stratos/ – Source Download available • White Paper – Selecting Platform as a Service – Platform as a Service TCO: multi-tenant shared container • Blog Articles – What is Platform as a Service? – PaaS Evaluation Framework for CIOs and Architects – How to simplify Platform as a Service Complexity – Searching for Cloud Reference Architecture • Contact us: – bizdev@wso2.com
- 35. Follow us: http://twitter.com/#!/wso2 Follow us: Contact us: http://twitter.com/#!/wso2 http://wso2.com/contact/ http://twitter.com/#!/cobiacomm
- 36. lean . enterprise . middleware