• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Up 2012   dave jilk - multi-tenancy in paa s (distribution version)

Up 2012 dave jilk - multi-tenancy in paa s (distribution version)






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



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

    Up 2012   dave jilk - multi-tenancy in paa s (distribution version) Up 2012 dave jilk - multi-tenancy in paa s (distribution version) Presentation Transcript

    • Multi-tenancy in PaaS Server PaaS vs. Resource PaaS Dave Jilk
    • Simplified PaaS ArchitectureDeveloper Application CodeService Platform
    • Why PaaS?Application Developer Strengths Not Application Developer StrengthsWriting application software Real estateNerd humor Generators Bandwidth contracts Hardware and cabling Networks Operating systems Web servers Language runtimes Application servers Databases Security
    • Early PaaS Univac 1100, circa 1975 Dial-up timesharing IDE: BASIC interpreter Code repository: Paper tape
    • Gartner Multi-Tenancy Model { Diagram from copyrighted Gartner materials }Source: Y. Natis, Gartner Reference Model for Elasticity and Multitenancy, June 2012
    • My Multitenancy Model Name Example Colocation Equinix Virtualization Rackspace Cloud Timesharing GoDaddy Container Heroku Tables Force.com
    • Cloud Pyramid Shared Container+SaaS Shared ?PaaSIaaS Shared Hardware
    • Overall Comparison Server PaaS Resource PaaS Examples EngineYard Heroku Multi-tenancy Shared-hardware Shared-containerScaling granularity Virtual machine Resource unit Configurability High to moderate Moderate to low Portability In: high Out: moderate In: low Out: moderate Isolation Hypervisor Operating System Filesystem Persistent or ephemeral Ephemeral or none Pricing per virtual machine per resource unit
    • Heroku Architecture Dyno: Linux process Scaling: Parallel dynosDiagram at: Isolation: Linux permissionshttp://www.royans.net/arch/wp-content/uploads/2010/01/image1.png Startup: ~2 seconds RAM Limit: 512 MB Response Timeout: 55 sec
    • Cloud Foundry Architecture Droplet: Linux user Scaling: Parallel dropletsDiagram at: Isolation: Linux Permissionshttp://cloudstory.in/wp-content/uploads/2012/01/cloudfo Startup: variableundry-architecture.png RAM Limit: as set Response Timeout: 30 sec
    • Engine Yard Architecture App Slave: Virtual machine Scaling: Parallel slavesDiagram at: Isolation: Virtualizationhttps://support.cloud.engineyard.com/attachments/token/mzorei9 Startup: provision + bootu4eifiuu/?name=cluster_architecture.png RAM Limit: as available Response Timeout: n/a
    • Scalability Server PaaS Resource PaaS Scaling speed Moderate FastResource increment Moderate Small Cost increment Moderate Small Scale limits Restrictive ModerateScaling algorithms Application specific General purpose Winner
    • Configurability Server PaaS Resource PaaS RAM limit As available on server Hard limitResponse time limit Not explicitly limited Hard limitTechnology stack Supported options or Supported options custom Stack add-ons Any Supported optionsStack configuration Flexible Very limited Location Potentially flexible Fixed Winner
    • Other issues to consider when selecting aPaaS that have nothing to do with whether it is a Server PaaS or a Resource PaaS• Language Support – Polyglot or single-language• External tool support – Databases – IDE integration• Application services support – Add-on marketplace• Hybrid scaling support
    • Generic PaaS Architecture End Users DeveloperRouting Service Controller Resource Resource Resource Resource Unit Unit Unit Unit Resource Resource Unit UnitCompute Pool
    • Compute Unit ArchitecturesServer PaaS Resource PaaS Virtual Machine Process Virtual Machine Process Virtual Machine ProcessPhysical Machine Virtual or Physical Machine Timesharing!
    • Compute Unit ArchitectureApplication Server on Resource or Server PaaS Thread ThreadExample:OpenShift Thread+ JBoss Application Server Process Virtual Machine Physical Machine
    • SynthesisServer PaaS Resource PaaS• “Inventory” of VMs • Larger selection of running common technology stack base configurations options and access to and resources configuration• Emphasize parameters standardized • VM affinity in resource configurations for units easier deployment • Addition of and management application server• Addition of functionality application server (database functionality connection pooling, transactions, message queues)