Track
Node.js
Review runtime boundaries, async I/O, HTTP lifecycle, logging, and process safety.
- 01
Runtime boundaries and entry points
Keep process startup separate from reusable application wiring.
runtimestartuparchitecture - 02
Async filesystem without blocking
Use async filesystem APIs in request paths so one slow disk read does not block the event loop.
filesystemasyncperformance - 03
Async failure boundaries
Handle rejected promises at the boundary where you can return a useful response.
errorsasynchttp - 04
Environment variables and configuration
Read and validate environment configuration once at startup.
configurationenvironmentstartup - 05
Module side effects and startup code
Avoid starting timers, connections, or jobs when a module is merely imported.
modulesside-effectsstartup - 06
Streams for large payloads
Stream large files or responses instead of loading everything into memory.
streamsmemoryhttp - 07
HTTP request lifecycle
Handle method checks, body limits, and response exits in a predictable order.
httprequestsvalidation - 08
Graceful shutdown and process signals
Stop accepting work and close resources when the process receives shutdown signals.
processshutdownsignals - 09
Structured logging
Log machine-readable events with request context and without sensitive data.
loggingobservabilitysecurity - 10
Input validation and path safety
Validate user input before using it in filesystem paths or other sensitive operations.
validationsecurityfilesystem