Member-only story

It works only on my machine: Containerization — Docker & K8s

Nikhil Verma
7 min readFeb 4, 2020
taken from google search images

I went through a really superb O’Reilly fake book image which I guess every developer wish to have in his/her kindle, if it existed in real. It jots down 1001 excuses under the umbrella excuse of “It works only on my machine.” But I guess this fake image can never be observed in real due to presence and nearly de facto standard in every company, the use of containerization engines. Above shared is the snapshot I had seen.

Gone are the days when people ship machines or call the developer to make the code start working on their own PC. People now a days write small micro services and deploy, following CI/CD pipeline to build & deliver fastly and important smartly without any excuse.

What existed before Containers? Virtual Machines(VMs)

Before Containers showed up, we used to use VMs to host our application, and I guess people liked it, because we were able to get a big server and slice it up to several VMs and have multiple computers and simulate a network. Now that Containers showed up, it seems like VMs aren’t a good idea anymore, because Containers give us a better level of abstraction than VMs.

--

--

Nikhil Verma
Nikhil Verma

Written by Nikhil Verma

Knowledge shared is knowledge squared | My Portfolio https://lihkinverma.github.io/portfolio/ | My blogs are living document, updated as I receive comments

No responses yet