setImmediate vs process.nextTick in Node.js

Introduction

These two functions help you run code after the current work is done, but they do it at different times. They let you control when your code runs next.

You want to run a function right after the current code finishes but before any I/O events.

You want to run a function after I/O events but as soon as possible.

You want to avoid blocking the main code and schedule small tasks efficiently.

Syntax

Node.js

process.nextTick(callback)

setImmediate(callback)

process.nextTick runs the callback before the event loop continues.

setImmediate runs the callback on the next cycle of the event loop.

Examples

This runs the callback immediately after the current operation, before any I/O.

Node.js

process.nextTick(() => {
  console.log('Runs before I/O events');
});

This runs the callback on the next event loop cycle, after I/O events.

Node.js

setImmediate(() => {
  console.log('Runs after I/O events');
});

Sample Program

This example shows the order of execution. process.nextTick runs before setImmediate, even though both are scheduled after the current code.

Node.js

console.log('Start');

process.nextTick(() => {
  console.log('Next Tick callback');
});

setImmediate(() => {
  console.log('Set Immediate callback');
});

console.log('End');

Important Notes

process.nextTick callbacks run before any I/O or timers, so use them for urgent tasks.

setImmediate callbacks run after I/O events, useful for deferring work without blocking I/O.

Using too many process.nextTick calls can starve I/O, so use carefully.

Summary

process.nextTick runs callbacks immediately after the current operation, before I/O.

setImmediate runs callbacks on the next event loop cycle, after I/O.

Choose based on when you want your code to run relative to I/O and timers.