What is docker and why will it change everything!

So what is all the all this Docker hype about? Software is multi-faceted, and getting it working on your dev-environment is one thing, but getting it into production presents many complicated challenges for dev-ops teams. Your software will always run in your labs against a set of external assumptions. This could be the operating system, a message queue, a database or even dependencies on the java and dot net run-times. The fact is that these external components to your software is often different in production, and all too often we see software failure, due to the external components no longer integrating correctly in the production environment.

In addition to this, we have to create rather complex installers, to navigate, the differences in the production environment, vs that in the test lab.  Sometimes your application will need to run on more than one server. Many enterprises will often have the need to scale up rapidly both in a vertical and horizontal manner, to deal with user demand for resources.  Overtime these environments will need to be upgraded, maintained and analysed for problem solving.  All of these things are the traditional challenges for a typical development operations department.

So how does docker change all of this? In its simplest form docker allows you to modularize your application into units of logical machine boundaries.  I will discuss container driven design later. The granularity of your module or docker service is an instance of your software AND the actual logical operating system with all its dependencies.

Docker containers spin up in seconds, and memory footprint is negligent, but the promise is, is that your software always runs exactly the same way in prod as in the lab.

Because docker containers are relatively small, it is possible to host thousands of these containers  over docker SWARM clusters potentially containing hundreds of nodes.

Docker provides an entire eco-system to manage, container distribution and management, which seamlessly aligns itself with the dev-op challenges.

The reason I believe that this technology will change everything is that both sides ultimately win. The vendor and the customer. Cost of ownership is radically reduces for the vendor, while the customer enjoys a superior security posture, better server density and a guarantee that the software will function correctly. For me this is the most compelling reason to learn docker, and get involved.

I am going to get more into these things in some future posts, with some very technical articles, on container orchestration engines such as Service Fabric, Kubernetes and SWARM. I will also demonstrate how to set up a cluster in Azure, create a load balances, configure reverse proxy containers to isolate all transport security concerns, and then integrate this with docker’s service discovery, to distribute load around the cluster. Fun times … stay tuned …  I will be doing all of this with the Microsoft stack.