NodeJS is evented (2nd line from the website), not single-threaded. It internally handles threading needed to do select/epoll/kqueue handling without the user explicitly having to manage that, but that doesn’t mean there is no thread usage within it.
More Related Contents:
- How to create threads in nodejs
- Which would be better for concurrent tasks on node.js? Fibers? Web-workers? or Threads?
- Grasping the Node JS alternative to multithreading
- What does it mean to say Apache spawns a thread per request, but node.js does not?
- How should I unit test multithreaded code?
- Understanding the Event Loop
- Difference between -pthread and -lpthread while compiling
- Does lock xchg have the same behavior as mfence?
- what is the correct way to implement a QThread… (example please…)
- CoreData: warning: Unable to load class named
- How to cancel Future in Scala?
- What is thread contention?
- How to make Qt work when main thread is busy?
- Does an x86 CPU reorder instructions?
- What is a “thread” (really)?
- Difference between the TPL & async/await (Thread handling)
- Doxygen is Slow
- Multi threading C# application with SQL Server database calls
- Running two threads at the same time
- How, if at all, do Erlang Processes map to Kernel Threads?
- Multithreading: What is the point of more threads than cores?
- How to detect and debug multi-threading problems?
- Thread references require static lifetime?
- Does multithreading make sense for IO-bound operations?
- Spring @Async limit number of threads
- Does an asynchronous call always create/call a new thread?
- Is it better to use TThread’s “Synchronize” or use Window Messages for IPC between main and child thread?
- What happens when different CPU cores write to the same RAM address without synchronization?
- Does multi-threading improve performance? How?
- Thread-safe in delphi