Think about how you find someone's phone number. You don't memorize a string of digits for every person you know. You save their name in your contacts, and your phone looks up the number for you. If that person gets a new number, you update the contact once, and every call still goes through correctly.

DNS (Domain Name System) does exactly this for the internet. You type google.com, and somewhere behind the scenes, that name gets turned into the actual address of a server (a number like 142.250.64.110), so your computer knows where to send the request.

JavaScript is single-threaded. One thread, one call stack, one thing at a time. And yet, Node.js handles thousands of concurrent connections without breaking a sweat. That seems like a contradiction — so how does it actually work?

The answer is the event loop.

First things first: Docker is not a virtual machine. It provides similar isolation benefits, but without virtualizing an entire operating system the way a VM does. This is a common misconception worth clearing up before we go any further.

So what is Docker, exactly? At its core, it's a process running on your Linux system — one that has been isolated from the rest of the machine in a way that makes it feel entirely self-contained. Instead of emulating a full kernel like a VM does, Docker isolates a single process using primitives built directly into the Linux kernel. Let's dig into how that actually works.

Hey there! Welcome to my blog.

I've decided to start documenting my journey as a software engineer. This space will be a place where I share what I'm learning, the challenges I run into, and the things I find interesting along the way.