Express Best Practices Checklist
On this page
Production Architecture With Express
Express does not dictate architecture, so you must. Keep handlers thin, move business logic into services, and isolate I/O into repositories. This separation improves testability and reduces incident risk.
Operational Must-Haves
- Graceful shutdown on SIGTERM (stop accepting new requests, finish in-flight)
- Timeouts and upstream cancellation where possible
- Health checks and readiness endpoints
- Centralized error mapping and stable client error codes
Performance and Safety
Most Express latency comes from downstream dependencies, not the framework. Optimize by caching correctly, minimizing unnecessary JSON serialization, and using connection pooling for databases.
Team Maintainability
Document routing and error contracts, enforce lint rules, and keep middleware order consistent across services. Consistency beats cleverness in production systems.