Embed Size (px)
Citation preview
PaaS is Dead.Brendan Burns
Software Engineer
Long live PaaS.Brendan Burns
Software Engineer - Microsoft Azure
o Source code to artifact
o Application oriented abstraction
o Value added APIs (esp. Storage)
o Deployment
o Healing
o Auto-scaling
What was PaaS(t)
o Source code to artifact - Docker
o Application oriented abstraction
o Value added APIs (esp. Storage)
o Deployment
o Healing
o Auto-scaling
What was PaaS(t)
o Source code to artifact - Docker
o Application oriented abstraction - Containers
o Value added APIs (esp. Storage)
o Deployment
o Healing
o Auto-scaling
What was PaaS(t)
o Source code to artifact - Docker
o Application oriented abstraction - Containers
o Value added APIs (esp. Storage) - Cloud APIs
o Deployment
o Healing
o Auto-scaling
What was PaaS(t)
o Source code to artifact - Docker
o Application oriented abstraction - Containers
o Value added APIs (esp. Storage) - Cloud APIs
o Deployment
o Healing - Container Orchestration
o Auto-scaling
What was PaaS(t)
o docker run …
What's left?
o Developer experience.
What's left?
o Building a PaaS is no longer a distributed systems problem.
o Pretty much anyone can stand on the shoulders of OSS tools*
* interpreted languages are easier
Occupy PaaS
o Building a PaaS is no longer a distributed systems problem.
o Pretty much anyone can stand on the shoulders of OSS tools**
** security is still a challenge for multi-tenant
Occupy PaaS
#!/bin/bash
while true; do
git pull origin production
sleep 5
done
Let‘s build a PaaS
FROM nodejs:6
node server.js
Let‘s build a PaaS
Let‘s build a PaaS
MyPaaS pod
Serve
Container
Sync
Container
Shared
Volume
Let‘s build a PaaS
MyPaaS pod
Serve
Container
Sync
Container
Shared
Volume
o PaaS creation is democratized
o More PaaSes will be built
o PaaS will be built by subject matter experts
o PaaS will be built by hobbyists
The future PaaS
o PaaS is becoming cloud native
o Built for containers
o Dependent on orchestration
The future PaaS
o PaaS is becoming a tool
o An “app” for your cluster, not a platform
o Choose the right one for the job..
o … or don‘t choose one at all.
The future PaaS
o PaaS is removing it‘s walls
o Access cloud APIs and external resources
o Drop down to orchestration APIs
o Eject vs. Gradual degradation
The future PaaS
The future is already here, it‘s just not very evenly distributed.
o WordPress (Publishing)
o Parse (Mobile Backend)
o SalesForce (CRM)
o Kong (APIs)
o …
What‘s next?
The future is already here, it‘s just not very evenly distributed.
o Parse (OSS)
o funktion
o Deis
o OpenShift
o …
What‘s next?
The future stack
Container Orchestration
CRM PaaS Marketplace PaaS API PaaS
Raw
Containers
The future stack
Container Orchestration
CRM PaaSMarketplace
PaaSAPI PaaS
Batch
Workloads
Storage
Workloads
Container orchestration is ~free.
PaaS are/will be mostly open source.
The future business
What will people (still) pay for?
o Pay for support
o Pay per request w/o lock-in
o Pay to remove whole departments (eg SRE)
o Pay for speed/agility (“it just works”)
The future business
PaaS is rightPaaS is wrong
Long Live PaaS
