A Node server is a set of streams and callbacks before it is an Express application. These lessons follow a municipal permit service through admission, export, analysis, and upstream calls. Each boundary has a measurable budget, a failure state, and a test that stays useful if the framework changes.
Topics in this track
- Node Incoming Body Limits and Abort State — Enforce wire-byte and parse budgets before an HTTP request becomes a domain command.
- Node Response Backpressure and Export Aborts — Couple export production to a slow response consumer and stop work when the client disconnects.
- Node CPU Work, Worker Pools, and Event Loop Delay — Move bounded CPU tasks off the request loop without creating an unbounded worker queue.
- Node Outbound Fetch Deadlines and Response Ownership — Give each upstream call a deadline, size budget, and response owner before composing an API reply.
Prerequisite paths
HTTP requests: keep method, status, and body contracts separate; Express Request and Process Boundaries; Streaming and Large Data Interfaces.
Practice and check
Build Project: Native Node Permit Gateway and review Web Development: Native Node Runtime Contracts.