---
title: "Discussion on \"Blocking vs Non-Blocking Code in Node.js\" | Hashnode"
description: "Discussion on \"Blocking vs Non-Blocking Code in Node.js\". Node.js is single-threaded. That's its design. And normally, that's fine.\nBut the moment one operation takes too long — and that thread sits there waiting — everything else in your server stops. No ot"
url: "https://hashnode.com/posts/blocking-vs-non-blocking-code-in-node-js/6a00d233e3eebc2e20b8ec22"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Blocking vs Non-Blocking Code in Node.js](https://kushagrablogs.hashnode.dev/blocking-vs-non-blocking-code-in-node-js?utm_source=hashnode&utm_medium=feed)

Node.js is single-threaded. That's its design. And normally, that's fine. But the moment one operation takes too long — and that thread sits there waiting — everything else in your server stops. No ot

May 10 · 5 min read · kushagrablogs.hashnode.dev  
Read the article

-   [#blocking-vs-non-blocking](https://hashnode.com/tag/blocking-vs-non-blocking)
-   [#blocking-vs-non-blocking-code-in-node-js](https://hashnode.com/tag/blocking-vs-non-blocking-code-in-node-js)

## Written by

[Kushagra Trivedi](https://hashnode.com/@kushagratrvd)

@kushagratrvd

  
[View profile](https://hashnode.com/@kushagratrvd)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.