Docker from day one

• gonna talk about docker, what it is and why you should adopt it now
• where to find me

Docker?

• So who knows what docker is?
• technically: combo of kernel features, cgroups and namespaces
• conceptually: you put your software in a box and it can then be put anywhere

• the new way
• It's moveable
• it's not a VM
• it's lighter than a VM
• same code path as code for host
• less isolation than with a vm

The Matrix from Hell

• Your product has N parts
• It must run on the developer's laptop
• ...and on the QA server
• ...and in this public cloud
• ...and on that private cloud
• ...and on a contributor's machine
• N parts x M contexts = big problem

• ok but what techical problem does it solve?
• the problem of standardisation
• (run thru the bullets here)
• the very powerful principle of least surprise
• one universal interface

Ok but why do I care?

• Ship and run anywhere
• With all dependencies
• With identical dev & prod envs
• Store, redeploy, rollback, always the same

• it can be run anywhere and everyone knows how to run it
• you can bridge public cloud and private cloud
• same environment in prod and dev
• phoenix deployment, no trash
• repeatable deploys
• no apt-get, npm installs

Docker on the backend

• base case
• compare to uberjar
• build it, push it, always the same, contained
• another more generic type of binary package
• portability and repeatable deployments
• linking and scaling
• mention databases

Demo time!

Docker on the frontend

• what can docker do for you?
• environment close to prod
• e.g. serve with nginx with same cfg
• no surprises
• idea: standardised versioned builder
• no npm woes

Demo time!

Thanks! Questions?

@ilkkalaukkanen

github.com/ilkka