Graceful Shutdown of Async Services

Graceful Shutdown of Async Services

In this lesson, you’ll learn how to catch system signals to ensure your background tasks finish their work before your Node.js process exits.

When you run a service, the operating system can send a signal—like SIGTERM—to tell your application it’s time to stop. By default, Node.js kills the process instantly. If your service is currently writing a file, processing a network request, or updating a database, an abrupt exit can leave data corrupted or tasks half-finished.

To prevent this, we intercept these signals using the process object. Instead of letting the app crash, we stop accepting new work and wait for the "in-flight" asynchronous operations to resolve.

Implementing a Clean Exit

Consider a scenario where you are processing a queue of events. You need to tell the system, "Finish what you're doing, then close the door."

let isShuttingDown = false;

process.on('SIGTERM', async () => {
  if (isShuttingDown) return;
  isShuttingDown = true;
  
  console.log('Shutdown signal received. Finishing tasks...');
  
  // Wait for the final async task to complete
  await finalizePendingWork();
  
  console.log('Cleanup complete. Exiting.');
  process.exit(0);
});

When the signal arrives, we set a flag (isShuttingDown) to reject new incoming requests (a form of manual load shedding). We then await the completion of existing logic. Only after those promises settle do we trigger process.exit(0).

This pattern ensures that your asynchronous services remain resilient. By coordinating the shutdown, you avoid the "race condition" of the process disappearing while your logic is still mid-execution. It turns a chaotic termination into a controlled, predictable event.

Key Takeaway: A graceful shutdown intercepts system termination signals to pause new input and wait for active asynchronous operations to complete before allowing the process to exit.