This document discusses the evolution of platform as a service (PaaS) over time. It argues that PaaS is no longer defined by proprietary platforms, as open source tools now allow developers to build their own PaaS solutions using containers and orchestration. The future of PaaS involves a more distributed model where specialized PaaS are built for different domains, and businesses may pay for support, usage-based pricing, or fully-managed services rather than proprietary platforms. Overall, the document suggests that PaaS as a concept is still relevant even if the traditional definition is changing.

1. PaaS is Dead.
Brendan Burns
Software Engineer

2. Long live PaaS.
Brendan Burns
Software Engineer - Microsoft Azure

3. 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)

4. 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)

5. 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)

6. 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)

7. 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)

8. o docker run …
What's left?

9. o Developer experience.
What's left?

10. 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

11. 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

12. #!/bin/bash
while true; do
git pull origin production
sleep 5
done
Let‘s build a PaaS

13. FROM nodejs:6
node server.js
Let‘s build a PaaS

14. Let‘s build a PaaS
MyPaaS pod
Serve
Container
Sync
Container
Shared
Volume

15. Let‘s build a PaaS
MyPaaS pod
Serve
Container
Sync
Container
Shared
Volume

16. 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

17. o PaaS is becoming cloud native
o Built for containers
o Dependent on orchestration
The future PaaS

18. 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

19. 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

20. 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?

21. 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?

22. The future stack
Container Orchestration
CRM PaaS Marketplace PaaS API PaaS
Raw
Containers

23. The future stack
Container Orchestration
CRM PaaS
Marketplace
PaaS
API PaaS
Batch
Workloads
Storage
Workloads

24. Container orchestration is ~free.
PaaS are/will be mostly open source.
The future business

25. 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

26. PaaS is right
PaaS is wrong
Long Live PaaS