Running Node.js in Production
summary
Claims that unhandled 'error' events crash the process so code must trap them and often call process.exit; shows that forgetting to catch socket/http errors and leaving listeners causes leaks and GC retention so use dot.once for one-shot handlers; demonstrates a monitor called forever that restarts child pids and displays uptime; describes require-analyzer that monkey-patches module.load to enumerate real dependencies; compares cluster shared-descriptor versus round-robin proxy for scaling and reports the proxy approach works in production.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:35Watch your Events
- 11:40Structure your code
- 12:57Option 1: Shared File Descriptors
- 13:37Option 2: Round-Robin Proxy
related talks
19mRunning Node.js in Production
30mNodeJS: Patterns and Tools to Ship to Production with Confidence
50mDebugging Node.js in Production
25mNode js applications diagnostics under the hood
20mAfter Years of Node in Production, We Still Block the Event Loop
30mNode.js Deep Debugging
19mNode.js Error Handling
22mScaling Node.js and unblocking the Event Loop