Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

The Open PaaS Stack

  • Soyez le premier à commenter

The Open PaaS Stack

  1. 1. Guy Korland
  2. 2. AGENDA PaaS, Defined Different Paths to PaaS What’s Missing? A (Slightly) Different Approach
  3. 3. THE CLOUD STACK - RECAP Manage applications and services Provision hosts/VMs
  4. 4. A PAAS TO SUCCESS?“There is a difference between knowing the PaaSand walking the PaaS…” Morpheus (with slight adaptations…)What do YOU expectout of PaaS?
  5. 5. WHAT DO I EXPECT OUT OF PAAS? I want to deploy my app (regardless of the stack I’m using)
  6. 6. WHAT DOES PAAS REALLY MEAN? Without fiddling with tedious installations of OS & middleware
  7. 7. WHAT DOES PAAS REALLY MEAN? Or host setup & provisioning 7
  8. 8. WHAT DOES PAAS REALLY MEAN?But still maintain the same development practices, full visibility, control & security
  9. 9. WHAT DOES PAAS REALLY MEAN? I want to be productive!
  10. 10. MANY PATHS TO PAAS
  11. 11. MANY PATHS TO PAAS
  12. 12. GOOGLE APP ENGINE
  13. 13. CONTROL ASSUMPTIONS Servers  Application Code Operating system – Selecting the language and stack of choice (Java/Python) Language (Java, Python, Go) Middleware stack (data store, app server, …) Architecture Scaling (Quotas: CPU, memory, network,..)
  14. 14. HEROKU
  15. 15. CONTROL ASSUMPTIONS Servers  Application Code Operating system  Selecting the middleware Language stack from a predefined list (Ruby/Java/Python/Scala/Clojure/NodeJS) Middleware stack (DB, app server, …) – Multiple choices, plugins Architecture Performance (Dyno)
  16. 16. AWS ELASTIC %
  17. 17. Control Assumptions Servers  Application Code Operating system  Selecting the middleware Language (Java, .NET, PHP) stack (anything beyond Apache/IIS) Middleware stack (tomcat, RDS, …)  OS configuration (if you want) – Can be easily extended  Performance Architecture (Web)  JVM tuning/configuration Storage
  18. 18. PRODUCTIVITY MYTHS You have to give up control for “…developing on GAE more simplicity introduced such a  Not always… design complexity that working around it pushes us 5 months Less code = more productivity behind schedule.”  Productivity is measured by units of features being delivered (not lines of code) Opinionated architectures (e.g. RoR/Grails) are extremely productive Carlos Bles post Goodbye Google App Engine
  19. 19. Head to Head ComparisonGAE, Heroku Amazon Top-down sandbox  Bottom-up approach approach  Designed for extreme Highly opinionated simplicity with a Extreme simplicity at the significantly higher degree expense of user control of control Only “long tail”, Fits a larger simple applications spectrum of apps
  20. 20. BUT STILL… Current offerings are limited by  The stacks they support  The environment on which they run Is this enough?
  21. 21. So What Makes for the Ideal PaaS?
  22. 22. OPEN any Stack, any Cloud (& OpenSource)
  23. 23. NON-INTRUSIVE Your app stays as is, you shouldn’t change the way you code
  24. 24. EXTENSIBLE Role your own stacks & auto-scaling rules
  25. 25. MANY PATHS TO PAAS
  26. 26. MANY PATHS TO PAAS
  27. 27. CLOUDFOUNDRY27
  28. 28. OPENSHIFT28
  29. 29. THE CHALLENGE (REALITY CHECK).. “Majority of businesses are planning to move their mission- critical apps to the cloud over the next two to five years” (HP Survey amongst 940 Need Responders) Only 5 percent have been able to migrate at least half of their applications to the cloud. By Reality the end of 2012, that number is expected to rise to 20% (Cisco Survey , 1300 Responders)29
  30. 30. CLOUDIFY30
  31. 31. CLOUDIFY31
  32. 32. GETTING STARTED…32 ® Copyright 2012 GigaSpaces Ltd. All Rights Reserved 32
  33. 33. Thank You!33

×