PaaS TCO
•Download as PPTX, PDF•
3 likes•1,782 views
Multi-tenant shared container PaaS will deliver a significant advantage when compared with single tenant, dedicated container PaaS. In single tenant, dedicated container PaaS, significantly more expense is required to run a PaaS environment compared with a multi-tenant, shared application container PaaS. The proposed PaaS cost evaluation tool compares multi-tenant, shared application container PaaS with single tenant, dedicated container PaaS (i.e. traditional application server deployment in Cloud) across multiple tenant counts and application platform service combinations. The worksheet incorporates application platform license (or subscription) cost, PaaS Management service cost, infrastructure expense, and IT management overhead. Across all scenarios, the worksheet calculates cost when application platforms are deployed on Infrastructure as a Service (IaaS).
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to PaaS TCO
Similar to PaaS TCO (20)
More from Chris Haddad
More from Chris Haddad (20)
Recently uploaded
Recently uploaded (20)
PaaS TCO
- 1. lean . enterprise . middleware Application Platform Multi-Tenancy and Platform as a Service Total Cost of Ownership (PaaS TCO) Chris Haddad Technology evangelism, strategy, and roadmaps Follow me @cobiacomm on Twitter Read more about our PaaS Story at blog.cobia.net/cobiacomm http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco- and-paas-roi-multi-tenant-shared-container-paas/ © WSO2 2011. Not for redistribution. Commercial in Confidence.
- 2. WSO2 Advantage • Platform as a Service hosts application servers, applications, business processes, APIs, services, and data • Cloud Washed PaaS • Provisions single-tenant, dedicated application server instances. • Partitions instances by tenant • Subscriber specifies number of application platform instances and topology (e.g. 4 Tomcat server instances, 1 mySQL database instance) • WSO2 Cloud Native PaaS • Provision multi-tenant, shared application platform service containers • Partition containers by service • Subscriber specifies application platform services and usage limits
- 3. PaaS 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
- 4. PaaS 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)
- 5. PaaS Architecture What is a partition? • Partitions define distinct container resource pools • Partition containers to tune container sharing, service resource allocation, QoS, and utilization • Containers may be assigned into service-specific or tenant specific partitions
- 6. Container Partitioning Single, flat namespace
- 7. Container Partitioning Multiple partitions and segmented name space
- 8. Container to Tenant Scaling Single Application Tenant per Dedicated Application Server Container
- 9. Container to Tenant Scaling Multiple Application Tenants per Shared Application Platform Service Container
- 10. 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
- 11. Partitioning and Tenancy Implications Five (5) Container Instances Tenant Application Solution Traffic Tenant- Tenant- Tenant- Tenant Partition 1 2 3 Container AS-1 ESB-1 AS-2 ESB-2 ESB-3 Tenant- Tenant- Tenant- Tenant- Tenant- Tenant Context 1 1 2 2 3
- 12. Partitioning and Tenancy Implications Three (3) Container Instances Tenant Application Solution Traffic Web Service Partition ESB Application Container ESB-1 ESB-2 AS-1 Tenant Context Tenant-1 Tenant-3 Tenant-2 Tenant-1 Tenant-2
- 13. PaaS Architecture Tenant Artifact Deployment • The PaaS deployer will provision tenant specific applications, services, and business process • The artifacts are deployed into one or more containers
- 14. PaaS Topology Decisions Containers may service a single tenant or multiple tenants • aPaaS Containers may deliver • a single service (e.g. web application hosting) or • multiple services (e.g. Enterprise Service Bus, web application hosting, database, identity) • aPaaS containers hosts database connection pools, resource bundles, mediators, and sessions resources • Containers are partitioned based on ability to isolate and share resources • Single tenant containers dedicate one or more containers for exclusive use by an application tenant (during a period of time) • Multi-tenant containers share containers across multiple simultaneous application tenants
- 15. Total Cost of Ownership Levers • Rapid elasticity • Provides ability to turn-on additional containers only when demand requires more capacity • Provides ability to turn-off under utilized containers and lower expense • Measured Service and Pay Per Use • No foundational infrastructure investment required • Possibly a minimal up-front registration investment • Only charged for usage (e.g. platform up-time, deployed application count, transaction count) • Resource Pooling • Minimize usage cost by sharing and re-using resources • On-demand self-service • Create and provision platform without third party participation
- 16. 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
- 17. 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
- 18. Attributes influencing Total Cost of Ownership • Container sharing and tenant isolation level • Tenant Density per JVM or Application Server • Container license cost Read entire methodology at http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas- roi-multi-tenant-shared-container-paas/
- 19. Platform as a Service Total Cost of Ownership Use Case 1: Complex solution, Low Tenant Count http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi- multi-tenant-shared-container-paas/
- 20. Platform as a Service Total Cost of Ownership Use Case 1: Complex solution, Low Tenant Count http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi- multi-tenant-shared-container-paas/
- 21. Platform as a Service Total Cost of Ownership Use Case 2: ESB-as-a-Service, Low Tenant Count http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi- multi-tenant-shared-container-paas/
- 22. Platform as a Service Total Cost of Ownership Use Case 2: ESB-as-a-Service, Low Tenant Count http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi- multi-tenant-shared-container-paas/
- 23. Follow us: http://twitter.com/#!/wso2 Follow us: Contact us: http://twitter.com/#!/wso2 http://wso2.com/contact/
- 24. lean . enterprise . middleware
Editor's Notes
- Containers host resourcesApplication platform as a service (aPaaS) containers Host database connection pools, resource bundles, network transport listeners, mediators, flows, sessionsPlatform as a Service (PaaS) containersHost application servers, database servers, Enterprise Service Bus serversInfrastructure as a service (IaaS) containers Host operating systems or file systems
- A single partition provides a flat name space (e.g. A-Z)
- Multiple partitions create name space segments (e.g. Partition-1.Resource1-3, Partition-2.Resource4-5, Partition-3.Resource7-8)
- Tenant = application
- Tenant = application or application component
- Service-level partitions are more efficientAll solutions deployed within a single partitionAll tenants deployed within a single partition