SSSoumyaditya Sinhainsoumyaditya-blog.hashnode.dev·May 8 · 4 min readThe Node.js Event Loop ExplainedNode.js runs on a single main thread. That sounds limiting, and in one sense it is. Only one thing can sit on the call stack at a time. But that is exactly why the event loop matters. It lets Node.js 00
SSSoumyaditya Sinhainsoumyaditya-blog.hashnode.dev·May 8 · 4 min readBlocking vs Non-Blocking Code in Node.jsWhen people first learn Node.js, they usually hear one sentence over and over: “Node.js is non-blocking.” Cool. But what does that actually mean? Because this one thing changes how your server behav00
SSSoumyaditya Sinhainsoumyaditya-blog.hashnode.dev·May 8 · 6 min readREST API Design Made Simple with Express.jsREST API design gets easier once you stop treating it like a pile of routes and start treating it like a set of resource actions. Express.js fits this model well because it keeps routing clear, readab00
SSSoumyaditya Sinhainsoumyaditya-blog.hashnode.dev·May 6 · 6 min readWhat is Middleware in Express and How It WorksWhen you first start learning Express, route handlers feel simple. You create a route, send a response, and everything works. app.get("/", (req, res) => { res.send("Hello World"); }); But real appl00
SSSoumyaditya Sinhainsoumyaditya-blog.hashnode.dev·May 6 · 6 min readNode.js: JavaScript on the serverJavaScript started in the browser. It lived inside web pages, clicked buttons, moved menus, and handled forms. That was the job. Then Node.js showed up and gave JavaScript a second life. Same language00
