2. RELEASE
INFRA
APP
BUILD/DEPLOY
2000 2010 2016
Weekly Daily Hourly
Single server VM’S Containers
FTP DevOps ?
Simple deployment
model. FTP code to
single server.
PH
Single app Multi Tiered Microservices
2xDB
APPAPPAPP
AB
C
Developer Abstractions
wercker
3. RELEASE
INFRA
APP
BUILD/DEPLOY
2000 2010 2016
Weekly Daily Hourly
Single server VM’S Containers
FTP DevOps ?
Simple deployment
model. FTP code to
single server.
PH
Single app Multi Tiered Microservices
2xDB
APPAPPAPP
AB
C
Daily releases at an increased scale
resulting in multiple applications and
databases on multiple virtual machines.
Developer Abstractions
wercker
4. RELEASE
INFRA
APP
BUILD/DEPLOY
2000 2010 2016
Weekly Daily Hourly
Single server VM’S Containers
FTP DevOps ?
Hourly releases, with applications being broken apart in smaller
responsibilities (microservices), are running on a large number of
servers in thousands of containers.
Simple deployment
model. FTP code to
single server.
Daily releases at an increased scale
resulting in multiple applications and
databases on multiple virtual machines.
PH
Single app Multi Tiered Microservices
2xDB
APPAPPAPP
AB
C
Developer Abstractions
wercker
5. All businesses are software businesses
Product velocity Opportunity cost
wercker
Business agility Competitive advantage
Value of Developer Productivity
6. All businesses are software businesses
Product velocity Opportunity cost
wercker
Business agility Competitive advantage
Value of Developer Productivity
7. All businesses are software businesses
Product velocity Opportunity cost
wercker
Business agility Competitive advantage
Value of Developer Productivity
8. All businesses are software businesses
Product velocity Opportunity cost
wercker
Business agility Competitive advantage
Value of Developer Productivity
17. Why naive?
We’re in flux. We’re in need of best practices and new tools.
Dockerfiles
1 container to rule them all
Build != Runtime containers
Fat containers
Tag your images
wercker
20. 1. You should create your containers programatically
2. You should be able to create as many pipelines as you want
3. Pipelines should be chainable
4. Pipelines should be able to build on each others artefacts
5. Pipelines should be able to run in parallel (fan in/ fan out)
6. Pipelines should be version controlled
7. Pipelines should be able to work cross-application
wercker
Conclusion
Key requirements for application delivery in Cloud Native world