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