Paying for PaaS

23
Paying for Platform as a Service © WSO2 2011. Not for redistribution. Commercial in Confidence. lean . enterprise . middleware 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/

description

 

Transcript of Paying for PaaS

Page 1: Paying for PaaS

Paying for Platform as a Service

© WSO2 2011. Not for redistribution. Commercial in Confidence.

lean . enterprise . middleware

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/

Page 2: Paying for PaaS

Measuring Value

• Time

• Cost

• Resources

Page 3: Paying for PaaS

What is your value baseline?

Page 4: Paying for PaaS

Running a Cloud Business

Measuring Revenue versus Cost

Source: http://giffconstable.com/2009/11/freemium-business-model-template/

Page 5: Paying for PaaS

Increasing Value: Cloud Objectives

• Financial Value

• Shift from capital expense into operational expense

• Pay only for what you use

• Efficiency Value

• Right-size solution footprint to match demand

• Pool resources and increase utilization

• Agility Value

• Reduce time to market through DevOps, automated governance, and on-

demand services

Page 6: Paying for PaaS

Cloud Business Value Blockers

• Silo owners

• Adoption curve

• Trust barrier

• Unknown baseline

• Funding model

Source: http://blog.industryweapon.com/2010/01/beware-of-the-business-blocker/

Page 7: Paying for PaaS

Cloud Business Value Blocker

Re-creating silos in the Cloud

Existing IT infrastructure

Page 8: Paying for PaaS

Cloud Application Platform Architecture

Cloud

Cloud Management

PaaS Manager

Cloud Governance

Identity Management

Asset Repositories (code, services, policies) IaaS

PaaS Run-time Framework (Stratos)

Service-aware, tenant-aware

Load Balancer

Stratos Controller

Asset/Code Deployer

Asset/Code Synchronizer

Metering and Billing

Cloud Native Container(s)

Tenant1 Tenant(n)

Page 9: Paying for PaaS

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

Page 10: Paying for PaaS

Partitions modify value proposition

Single, flat namespace Multiple partitions and segmented name space

Page 11: Paying for PaaS

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)

Page 12: Paying for PaaS

Tenant Scaling Method Impacts Value Proposition

Single Application Tenant

per

Dedicated Application

Server Container

Multiple Application Tenants per

Shared Application Platform Service Container

Page 13: Paying for PaaS

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

Page 14: Paying for PaaS

Cloud Topology and Value

Tenant Context

Container

Tenant Partition

Application Solution Tenant Traffic

Tenant-1

AS-1

Tenant-1

ESB-1

Tenant-1

Tenant-2

AS-2

Tenant-2

ESB-2

Tenant-2

Tenant-3

ESB-3

Tenant-3

Five (5) Container Instances, Three Tenants

Page 15: Paying for PaaS

Partitioning and Tenancy Implications

Tenant Context

Container

Service Partition

Application Solution Tenant Traffic

ESB

ESB-1

Tenant-1 Tenant-3

ESB-2

Tenant-2

Web Application

AS-1

Tenant-1 Tenant-2

Three (3) Container Instances, Three Tenants

Page 16: Paying for PaaS

Platform as a Service Total Cost of Ownership

http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi-multi-tenant-shared-container-paas/

Use Case: ESB-as-a-Service, HighTenant Count

Page 17: Paying for PaaS

http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi-multi-tenant-shared-container-paas/

Platform as a Service Total Cost of Ownership

Use Case: ESB-as-a-Service, High Tenant Count

Page 18: Paying for PaaS

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

Page 19: Paying for PaaS

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

Page 20: Paying for PaaS

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/

Page 21: Paying for PaaS

Resources

• WSO2 Stratos • http://wso2.com/cloud/stratos/

• Cloud Value • PaaS Total Cost of Ownership White Paper

Page 22: Paying for PaaS

Contact us:

http://wso2.com/contact/

Follow us:

http://twitter.com/#!/wso2

Page 23: Paying for PaaS

lean . enterprise . middleware