AKAbhishek Kumarinorion-blogs.hashnode.dev·May 9 · 9 min readThe Node.js Event Loop — How One Thread Handles Everything Node.js runs on a single thread. Here's the clever mechanism that lets it serve thousands of requests anyway. Here's a question that puzzles most Node.js beginners: "If Node.js runs on a single thre00
AKAbhishek Kumarinorion-blogs.hashnode.dev·May 9 · 7 min read`this`, `call()`, `apply()`, and `bind()` in JavaScript — Finally Explained Clearlythis is one of those things every JavaScript developer uses but few can confidently explain. Once it clicks, call, apply, and bind make complete sense. Until then, it's just guesswork. What Is this? 00
AKAbhishek Kumarinorion-blogs.hashnode.dev·May 9 · 11 min readModems, Routers, Switches & More: The Hardware Behind Every Web RequestWhen you deploy an API to production, requests don't teleport from a browser to your server. They travel through physical hardware — modems, routers, switches, firewalls, load balancers — each one pla00
AKAbhishek Kumarinorion-blogs.hashnode.dev·May 9 · 8 min readJavaScript Functions — Declarations, Expressions, and the Hoisting SurpriseEverything you need to write clean, reusable code — and understand why calling a function too early sometimes works and sometimes doesn't. Imagine you're building a tip calculator. Every time a user 00
AKAbhishek Kumarinorion-blogs.hashnode.dev·May 9 · 7 min readBlocking vs Non-Blocking Code in Node.js — Why It Matters for Every ServerTwo servers. Same hardware. Same task. One handles 10 users smoothly. The other grinds to a halt. The difference isn't the language, the framework, or the database. It's whether the code blocks or not00
