The Event Loop Fairytale
summary
Clear walkthrough of how Node.js actually schedules work: the event loop runs six-ish phases (timers, I/O callbacks, poll, check, close) while process.nextTick and microtasks run between phases, so you control ordering; console.log runs synchronously before timers; nonblocking I/O gets handed to the libuv thread pool (file reads, DB calls) and returns out of order; use setImmediate, setTimeout and promises deliberately and avoid blocking the loop — examples show when things reorder and why misusing nextTick slows the app.
AI-written summary · about
chapters (13)
- 0:00Welcome and introduction
- 2:10The age of blocking dragons
- 4:37The rise of Node.js
- 6:03The land of promises
- 8:14Meet the event loop guardians
- 10:00How the event loop works
- 13:52The magic of libuv forest
- 17:47Understanding blocking dragons
- 18:52The six phases of the event loop
- 23:01Diving into loop phases
- 26:53Mastering microtask control
- 28:42Synchronous vs asynchronous calls
- 30:26The power and limits of tricks
