Node.js worker_threads
Ranked 9 of 11 concurrency libraries by recommenders
Recommended for running JavaScript work in parallel threads with message passing and easy bolt-on use. Most common caveat is awkward ergonomics and costly data serialization between threads.
Recommended for running JavaScript work in parallel threads with message passing and easy bolt-on use. Most common caveat is awkward ergonomics and costly data serialization between threads.
11 people gave an opinion
- recommend it
- 6
- criticize it
- 5
- approval share
- 55%
Recommended in 3 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 1.2 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 3 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
What people warn about
Each mark is one comment
Awkward ergonomics and complicated API
“The friction mainly comes from ergonomics, as pointed out in the article.”
Comment from 22 Mar 2026 in “Node.js worker threads are problematic, but they work great for us” “the api is kind of low-yet-high-level and that brings some complications”
Comment from 22 Mar 2026 in “Node.js worker threads are problematic, but they work great for us” Serialization cost and weak backpressure
“The lack of backpressure handling nor promise api for postMessage is also quite annoying, I had many OOMs because of it.”
Comment from 22 Mar 2026 in “Node.js worker threads are problematic, but they work great for us” “The serialization cost of passing data between threads ate most of my gains”
Comment from 22 Mar 2026 in “Node.js worker threads are problematic, but they work great for us”
Other concurrency libraries people recommend
The four most recommended other concurrency libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Tokio | 57 | 45 | 56% | 12 | — | — |
| Akka | 12 | 9 | 57% | 7 | — | — |
| ZIO | 11 | 2 | 85% | 9 | — | Approved |
| Trio Python library | 10 | 0 | 100% | 8 | — | Approved |
| Node.js worker_threadsThis page | 6 | 5 | 55% | 3 | — | — |
What people said
All 11 comments that mention it, newest first. Each links to the original comment.
“JS's solution is much better, it has worker threads with message passing mechanisms”
“the api is kind of low-yet-high-level and that brings some complications”
“The friction mainly comes from ergonomics, as pointed out in the article.”
“it does work and sometimes it's easier to write and reason about”
“The worker situation would be much better with inline workers (or modules).”
“The lack of backpressure handling nor promise api for postMessage is also quite annoying, I had many OOMs because of it.”
“Worker threads can be more convenient than FFI, as you don't need to compile anything, you can reuse the main application's functions”
“I'm using worker_threads + SharedArrayBuffer and running them in Bun.”
“The serialization cost of passing data between threads ate most of my gains”
“Worker threads can't handle I/O”
“very easy to bolt on to an existing plain http app”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.