Event Loop

Definition

The event loop is the mechanism that allows a single-threaded runtime, like JavaScript's, to handle asynchronous operations by continuously checking a queue of pending callbacks and executing them one at a time once the current stack of synchronous code has finished running.

Overview

The event loop is the runtime mechanism that makes asynchronous programming possible on a single thread. At a high level, a JavaScript runtime maintains a call stack for currently executing synchronous code, and delegates operations like timers, network requests, and file I/O to the underlying platform (the browser or Node.js's libuv library). When one of those operations completes, its associated callback is placed into a queue rather than executed immediately. The event loop's job is simple but essential: continuously check whether the call stack is empty, and if so, pull the next callback from the queue and execute it. A subtlety that trips up many developers is that JavaScript actually has multiple queues with different priorities. Microtasks — including resolved Promise callbacks — are processed before macrotasks like `setTimeout` callbacks, and the entire microtask queue is drained completely between each macrotask. This is why a `Promise.resolve().then(...)` callback reliably runs before a `setTimeout(..., 0)` callback, even though both were scheduled to run 'as soon as possible.' Because the event loop only processes one callback at a time on a single thread, a long-running synchronous operation — like a computation-heavy loop — blocks the entire event loop, preventing any other callbacks, including UI updates or incoming requests, from running until it finishes. This is a key reason CPU-intensive work is often offloaded to worker threads or separate processes rather than run directly on the main thread in JavaScript environments. Understanding the event loop is essential for debugging timing-related bugs in JavaScript and Node.js applications, and it's a frequently tested concept in front-end and Node.js technical interviews precisely because its behavior — while conceptually simple — has enough subtlety in queue ordering to trip up experienced developers. It is often mentioned alongside JavaScript in this space. It is often mentioned alongside Concurrency in this space.

Key Concepts

• Continuously checks if the call stack is empty and executes queued callbacks
• Enables single-threaded asynchronous programming without OS-level threads
• Distinguishes microtasks (Promises) from macrotasks (setTimeout, I/O callbacks)
• Microtask queue is fully drained before the next macrotask executes
• Long-running synchronous code blocks the entire event loop
• Implemented differently across environments (browser vs. Node.js/libuv)
• Core mechanism underlying JavaScript's non-blocking I/O model

Use Cases

Frequently Asked Questions

Related in Programming