Summer School - Demonstrating Cloud Value

Summer School - Demonstrating Cloud Value






Total Views
Views on SlideShare
Embed Views



3 Embeds 122 104 9 9



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Summer School - Demonstrating Cloud Value  Summer School - Demonstrating Cloud Value Presentation Transcript

  • 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 and-paas-roi-multi-tenant-shared-container-paas/ © WSO2 2011. Not for redistribution. Commercial in Confidence.
  • Measuring Value • Time • Cost • Resources
  • What is your value baseline?
  • Running a Cloud Business Measuring Revenue versus CostSource:
  • 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
  • Cloud Business Value Blockers • Silo owners • Adoption curve • Trust barrier • Unknown baseline • Funding modelSource:
  • Overcoming Cloud Value Blockers: WSO2 AppFactory
  • 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
  • Cloud Application Platform ArchitectureCloud PaaS Run-time Framework (Stratos) Cloud Management Service-aware, tenant-aware Load Balancer Stratos ControllerPaaS 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
  • PaaS ArchitectureWhat 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
  • Partitions modify value proposition Multiple partitions and Single, flat namespace segmented name space
  • Tenant Scaling Method Impacts Value PropositionSingle Application Tenant Multiple Application Tenants per per Shared Application Platform Dedicated Application Service Container Server Container
  • 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
  • Cloud Topology and ValueFive (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
  • Partitioning and Tenancy ImplicationsThree (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
  • Platform as a Service Total Cost of Ownership Use Case: ESB-as-a-Service, HighTenant Count
  • Platform as a Service Total Cost of Ownership Use Case: ESB-as-a-Service, High Tenant Count
  • 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
  • Resources• WSO2 Stratos •• WSO2 AppFactory • • What is AppFactory? Blog post• Cloud Value • PaaS Total Cost of Ownership White Paper
  • Follow us:Contact us:!/wso2
  • lean . enterprise . middleware