Terms:
OS: Operating System
VM: Virtual Machine
Server: Big olâ hunk of metal with some wiry bits
Orchestrator: Something that runs on a website and manages what everything does
Messaging system: Not MSN⌠in a website, the messaging service essentially runs back and forth between different components and pieces of your site and takes messages from one thing to the other.
Host OS: The base operating system for your machine
Guest OS: Created by a VM
Iâm going to set a scene here that we are going to keep referring back to.
Youâve built a website for a big idea. Itâs got a form that a user can submit, and itâs got a bunch of other snazzy features. You are very pleased with this and want to take the idea further. You need some help from Randall the developer. Randall is a cool guy. He loves burritos đŻ
To build your website, you are running 3 different OSs, as your essential apps and features run on different operating systems.
Essential app A: Linux version 6.6
Essential app B: Windows
Essential app C: Linux version 5.1
Before we jump straight into Docker, I think itâs important to have some historical context.
Before Docker, and before containers, data was stored and accessed on servers, which are stored in giant fridges called data centres. Every one of these servers holds 1 OS, and they are pretty expensive.
Back to you and Randall. On top of paying Randall for his excellent skills, youâre paying top dollar for three servers! Thatâs 3 big hunks of metal, and 3 payments to store them in a data center! Thatâs going to add up $$$âŚ
This is why hypervisors were invented.
Hyper...what?
Hypervisors are essentially used to split up the memory and storage on a server. This means that you can have one server for multpile OS systems. Oooooooohhhhhhhhh. Exciting stuff.
Let me explain:
Imagine for a second that your server has turned into a big rectangular pizza.
Stay with me, stop thinking about pizzaâŚ
âYou have 3 very fussy people coming over for dinner. You need to feed them all. They all eat different things, and donât like anything else. You also need to eat - so what will you do? Itâll be very expensive to make 4 different pizzas...
You are going to make one huge pizza, but with 4 different flavours in each corner. You decide on the topping, and the amount of toppings, and then bake it in the oven.â
Now Iâll say that analogy again but with some different words
âYou have 3 important applications that run in your website. They all require an OS. They all run on a different OS, they canât run on anything else. Remember your 3 servers? Itâs very expensive to run and keep them all. Your website is also running through something - called Node.js. This is a little more flexible and can run through most OSs.
You are going to have one server, but with 4 different OS running on it. You can also decide on the distribution of resources such as CPU, RAM, and all sorts.â
This is basically what a hypervisor does - you can split your resource (your server) to run multiple OS and assign it as much memory and power as you need (limited to the capacity of your server.) - this way you can run all of your applications (feed all of your fussy guests) on one server, rather than having multiple servers!
A hypervisor also sits under your VMs and provides the base for them. You may have heard of VMs before. Say you and Randall are running your website on your Linux machine, but you really need an application in your site that runs only on Windows. Uh oh. But itâs ok because VMs exist! You can spin up a Windows machine inside your Linux machineâŚ.. Confusing. But that is what hypervisors and other VMs do.
The most popular type of hypervisor is VMware, specifically ESXi.
Great, but does that explain Docker?
No.
Docker is actually more like a single server with a hypervisor on top...
The big difference is that a VM virtualises the hardware - this causes the OS to believe that it in fact does have the correct hardware (kernel) to do what it needs to do. In essence, the VM is âfoolingâ the OS.
Docker, on the other hand, sees what you want to run, and then provides an interface for the programs inside it (that all run on different versions and are a nightmare). It puts them into little virtual boxes, or containers. It is similar to how a VM would do it, but it is itâs own little box, rather than a virtualisation of hardware, and the creation of a âguest OSâ (tricking the host OS into thinking it has the ability to run) And it will perform better doing this due to the fact that it uses the base OS kernel, rather than creating something on top of it as a VM does.
Kernel�
The kernel is a computer program at the core of your computer's OS with complete control over everything in the system. Every OS has one. Your Windows computer has a Windows kernel, your Ubuntu system has a Linux kernel and so on.
You can read more about the kernel in this article
So why is Docker so popular?
Why is the industry going mad for docker right now?
- Faster onboarding
This point is pretty self explanatory.
Let's go back to you and Randall.
We already know that you have a Linux machine and you have built your site with Node. So Randall needs to install and get Node up and running. You also have a form on the site, and behind that is a database. So Randall needs to install and get familiar with MongoDB, which you have used. Randall also needs to download, install and get familiar with the site orchestrator and the messaging system
Thatâs quite a lot to do, and you havenât even started with Randall on your vision for this workâŚ
Letâs pull this scenario over to a universe where you are using Docker.
Hereâs that same scenario:
Randall needs to install and get familiar with Docker.
Thatâs...it.
You can get on with explaining your vision for your website.
- Itâs portable
This may sound strange, as it may feel like everything on the internet is portable - that is, you can access stuff on pretty much any machineâŚ
You know that joke of developers saying to testers âwell, it works on my machine!â?
If they arenât using docker, then it might be true! We already learned from Randall that some things on your website require different OSs, and have different dependencies (above the kernel level) to run⌠so if a developer builds a lovely shiny thing and doesnât build it through docker, then they are relying on everyone that they send it to having the necessary stuff in order to run it!
Docker just wraps all of the code up in OS boxes, or containers, and runs them everywhere and anywhere! This also means that the code can be built by Docker anywhere, allowing for more fluid collaboration between teams.
You must be careful though - if you and Randall build something that references something external, Docker wonât be able to put that into a container - so it may not work as expected on another machine that doesnât have the external thing
- Itâs fast....
So it isnât technically true that Docker is faster than VMs, but it performs better due to the fact that Docker shares the host kernel - it is more efficient and therefore your computer will run smoother - I suppose this gives the impression that it is faster.
It is not wrong to say that it is faster - technically it is - but Iâll leave it up to you if you want to start a fight with someone about it! Ok so it is faster, but it is faster because of the better performance, not because it is inherently just faster.Inside the container (where your website and its contents are happily running), it performs about the same as a VM, but the act of actually having a VM running on your machine is quite performance draining.
To sum up - Docker is essentially a speedy burrito, full of code.
đŻ
Thank you to:
Many YouTube videos, particularly
Network Chuck - https://www.youtube.com/watch?v=eGz9DS-aIeY
Many folks on Twitter, particularly:
@mesetatron - for your incredible subject knowledge and clarity of points
âď¸Coffee - a staple of my diet
đľTea - so many cups of tea
đŚIce cream - 1 tub of ice cream was consumed!
Oldest comments (34)
That was a really good article. Thank you for sharing!
I'm glad you enjoyed it!
MSN?! The nostalgia is strong here! I'm interested in understanding docker more, so I'll read fully after sleep
Haha it was the first thing I thought when I learned about messengers!
This was a helpful intro for me! Thanks for sharing!
Very good article. Thanks
I recently made an intro video discussing containers, docker, and kubernetes. Hope it helps someone.
youtube.com/watch?v=3f5wWYLWOtQ
Awesome article! Been wanting to learn docker for some time and this provided a well-described overview of what it can do.
Great explanation! Thanks for sharing.
Finally, my brain understood docker.thanks
That was well written thanks
what a fun way to describe Docker. Do we need a Randall then? I'm learning Docker but I really prefer to work on frontend and backend. I'm doing my best to keep learning and not give up
I think we all need a Randall... I bet they know about docker...