Node.js - Part Five - No JS Redpool

There are cases where asynchronous ready based eventing is not possible. DNS lockups, file IO and user specified workload can use the thread pool. Some CPU intensive libraries in nodes such as the crypto library uses the thread pool too. Calling this function will block the event main loop. It's possible not to use the synchronous version of read file and opt in for the synchronous one. Those calls ends in sync, S-Y-N-C. For example, fs.readfile sync will call the read directly and will block. It will not use the thread Pool.