---
title: "Discussion on \"Blocking vs. Non-Blocking: The Engine of Node.js Performance\" | Hashnode"
description: "Discussion on \"Blocking vs. Non-Blocking: The Engine of Node.js Performance\". In traditional programming, code executes line-by-line. If one line takes a long time, everything behind it stops. In Node.js, we have two ways to handle these \"slow\" tasks: Blocking and Non-Blocking."
url: "https://hashnode.com/posts/blocking-vs-non-blocking-the-engine-of-node-js-performance/6a009996e3eebc2e208eafcd"
---

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

Discussion

# [Blocking vs. Non-Blocking: The Engine of Node.js Performance](https://understand-and-build-in-web.hashnode.dev/blocking-vs-non-blocking-the-engine-of-node-js-performance?utm_source=hashnode&utm_medium=feed)

In traditional programming, code executes line-by-line. If one line takes a long time, everything behind it stops. In Node.js, we have two ways to handle these "slow" tasks: Blocking and Non-Blocking.

May 10 · 3 min read · understand-and-build-in-web.hashnode.dev  
Read the article

-   [#blocking-vs-non-blocking](https://hashnode.com/tag/blocking-vs-non-blocking)
-   [#blocking](https://hashnode.com/tag/blocking)
-   [#non-blocking](https://hashnode.com/tag/non-blocking)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#chaicode](https://hashnode.com/tag/chaicode)
-   [#chaiaurcode](https://hashnode.com/tag/chaiaurcode)
-   [#chaicohort](https://hashnode.com/tag/chaicohort)
-   [#computer-science](https://hashnode.com/tag/computer-science)

## Written by

[ARKPARAVA CHAKRABORTY](https://hashnode.com/@arkapravachakraborty)

@arkapravachakraborty

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

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
