Don't write spaghetti code in server side JavaScript
summary
Core claim is simple and actionable: don't block the event loop or a long callback prevents any other events from running so timers and network callbacks never fire. Examples use Node's EventEmitter, setTimeout and a busy while loop to demonstrate the failure mode, and note Node handles thousands of concurrent connections only if callbacks are short. Recommended pattern is concrete: create request objects with named functions and factory methods to encapsulate state and free memory. A proof of concept is a DNS server in node that runs but feels "scary" to implement.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:58The Event Loop Postman
- 7:19Event Emitter
- 11:12Cli Pipes
- 16:10Streams
- 18:13Encapsulate
- 19:18Document Your Flow Callbacks
