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

926 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
926
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

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

  1. 1. Multi-tenancy in PaaS Server PaaS vs. Resource PaaS Dave Jilk
  2. 2. THE ESSENCE OF PAAS
  3. 3. Simplified PaaS ArchitectureDeveloper Application CodeService Platform
  4. 4. 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
  5. 5. Early PaaS Univac 1100, circa 1975 Dial-up timesharing IDE: BASIC interpreter Code repository: Paper tape
  6. 6. MULTI-TENANCY
  7. 7. Gartner Multi-Tenancy Model { Diagram from copyrighted Gartner materials }Source: Y. Natis, Gartner Reference Model for Elasticity and Multitenancy, June 2012
  8. 8. My Multitenancy Model Name Example Colocation Equinix Virtualization Rackspace Cloud Timesharing GoDaddy Container Heroku Tables Force.com
  9. 9. Cloud Pyramid Shared Container+SaaS Shared ?PaaSIaaS Shared Hardware
  10. 10. A COMPARISON
  11. 11. 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
  12. 12. 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
  13. 13. 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
  14. 14. 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
  15. 15. 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
  16. 16. 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
  17. 17. 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
  18. 18. THE FUTURE
  19. 19. Generic PaaS Architecture End Users DeveloperRouting Service Controller Resource Resource Resource Resource Unit Unit Unit Unit Resource Resource Unit UnitCompute Pool
  20. 20. Compute Unit ArchitecturesServer PaaS Resource PaaS Virtual Machine Process Virtual Machine Process Virtual Machine ProcessPhysical Machine Virtual or Physical Machine Timesharing!
  21. 21. Compute Unit ArchitectureApplication Server on Resource or Server PaaS Thread ThreadExample:OpenShift Thread+ JBoss Application Server Process Virtual Machine Physical Machine
  22. 22. 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)

×