History#
One App to One Server Then Virtualization came along. virtual cpu, virtual memory, virtual disks, virtual networking, etc OS overhead and licensing are potential issues with virtualization, admin, patching, updates, antivirus Squeezed more out of hardware that was being underutilized though, “Hypervisors revolutionized IT.” Then came along containers. One Server, One OS, Containers are slices of the OS More efficient than VM’s, and frees up resources.
Virtualization - The Good Let us Keep our existing apps Simple Migrations Made Life Easy
Virtualization - The Bad Let us Keep our existing apps We’ve still got our legacy apps
Docker Modernize Traditional Apps - some apps can be migrated directly to containers
Cloud Native -
Dockers makes running applications in containers very easy.
Stateful (really starting to be great in ~2018)
- Has to remember stuff
Stateless
- Doesn’t remember stuff
The ability to adapt and change is vital to modern businesses
- Proactive
- Reactive
- Agile
- Scalable
- Resilient
Containers, it is possible to deploy some of our legacy apps directly inside of containers… This should not be the end goal.
Containers, The Good Modern Scalable Self-healing Portable
Container, The Bad It will take effort to take advantage
Alpha Features are off by default Early Code Uncertain Future Not for Production
Beta On by Default Becoming Stable Promising Future Some details may change
GA Production Ready Solid Future Stable Code Features
Ecosystem - perform your due diligence
Orchestration - Make sure to have the game plan documented and in a version control system (Describes the App) Ordered Startups Intelligent Scheduling
Conferences Dockercon Kubecon