This document discusses how platform-as-a-service (PaaS) architectures can maximize business value by enabling efficient sharing of computing resources across multiple application tenants. It describes how partitioning containers and applications into logical groups allows optimizing utilization while maintaining performance and isolation. Key metrics for measuring value include deployment speed, scalability, and cost of operations per user or transaction.

1. lean . enterprise . middleware
Demonstrating Cloud Value
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. Measuring Value
• Time
• Cost
• Resources

3. What is your value baseline?

4. Running a Cloud Business
Measuring Revenue versus Cost
Source: http://giffconstable.com/2009/11/freemium-business-model-template/

5. 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

6. 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/

7. Overcoming Cloud Value Blockers: WSO2 AppFactory

8. Architecture Shapes Value
• Resource friendly := small footprint, minimal consumption,
parallelizable workloads
• Poolablility := Non-exclusive use, short usage duration
• Automation := decrease activity time, latency between steps
• Governance := encourage trust, communication, coordination
• Distribution friendly:= Stateless, autonomous

9. Cloud Application Platform Architecture
Cloud
PaaS Run-time Framework (Stratos)
Cloud
Management Service-aware, tenant-aware
Load Balancer
Stratos Controller
PaaS Manager
Cloud Native Container(s)
Asset/Code Deployer
Cloud
Governance
Asset/Code Synchronizer Tenant1 Tenant(n)
Metering and Billing
Asset Repositories (code, Identity
services, policies) Management IaaS

10. 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

11. Partitions modify value proposition
Multiple partitions and
Single, flat namespace segmented name space

12. Tenant Scaling Method Impacts Value Proposition
Single Application Tenant Multiple Application Tenants
per per
Shared Application Platform
Dedicated Application Service Container
Server Container

13. 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

14. Cloud Topology and Value
Five (5) Container Instances, Three Tenants
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

15. Partitioning and Tenancy Implications
Three (3) Container Instances, Three Tenants
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

16. Platform as a Service Total Cost of Ownership
Use Case: ESB-as-a-Service, HighTenant Count
http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi-
multi-tenant-shared-container-paas/

17. Platform as a Service Total Cost of Ownership
Use Case: ESB-as-a-Service, High Tenant Count
http://blog.cobia.net/cobiacomm/2012/05/13/paas-tco-and-paas-roi-
multi-tenant-shared-container-paas/

18. Key Value Metrics
• Foundation
• Time to create new application environment
• Time to redeploy application
• Optimize
• Minimum and maximum scale
• Scale frequency (i.e. time to scale up/down)
• Transformation
• Time and effort required integrating business process, event
processor – creating a complex app.
• Time and effort required to apply policy across tenant(s)
• Cost to operate application per user or transaction

19. Resources
• WSO2 Stratos
• http://wso2.com/cloud/stratos/
• WSO2 AppFactory
• http://wso2.com/solutions/app-factory/
• What is AppFactory? Blog post
• Cloud Value
• PaaS Total Cost of Ownership White Paper

20. Follow us:
Contact us:
http://twitter.com/#!/wso2
http://wso2.com/contact/

21. lean . enterprise . middleware