11. Simpler scaling
This still requires you to build your applications
correctly.
Though it makes it easier to do so.
Doesn't make the application magically scale
12. Allows you to run multiple version of a program on
one server
Even from different distribution.
ie. Apache 2.2 from Ubuntu and Apache 2.4 from
fedora.
13. Downsides
• Requires more storage
• Uses more memory as no sharing between
applications in different containers (Far less than
multiple virtual servers)
• Higher complexity for simple systems.
14. Why now
• Developer/Human time is becoming the most
expensive resource.
• Reduce complexity at cost of storage/some
memory
• Though fart less memory than a VM
15. Downsides
• Only linux (For now)
• Requires up to date kernel
• Images don't work across cpu architectures. ie Arm
and AMD64
• You can use the same docker file to build a new
image
• Its new and it works diffrently
16. What doesn't it solve
• Replication/Resiliency
• Bad code
• Its a tool that help with specific problems
• Its not a magic bullet
17. How do you to play with it
• Vagrant
• http://www.vagrantup.com
• Docker Machine (Boot2Docker)
• https://docs.docker.com/machine/
19. Some definitions before we start
Image:
This is the snapshot or what your
running container will be created from.
Also can be used as the start of a new image.
Similar to a class in programming
20. Some definitions before we start
Container:
Running instance of an image.
Similar to and object in
programming.