Page 3
What is your value baseline?
Page 4
Running a Cloud Business
Measuring Revenue versus Cost
Source: http://giffconstable.com/2009/11/freemium-business-model-template/
Page 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
Page 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/
Page 7
Overcoming Cloud Value Blockers: WSO2 AppFactory
Page 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
Page 9
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 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
Page 11
Partitions modify value proposition
Single, flat namespace Multiple partitions and segmented name space
Page 12
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
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
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
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 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
Page 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
Page 20
Contact us:
http://wso2.com/contact/
Follow us:
http://twitter.com/#!/wso2
Page 21
lean . enterprise . middleware