Case Studies Best Practices
A condensed summary of the 25 most important case study practices for Node.js teams - how to read, write, and maintain reference architectures and before/after stories.
//
Search across all documentation pages
A condensed summary of the 25 most important case study practices for Node.js teams - how to read, write, and maintain reference architectures and before/after stories.
Annotate Node LTS version: Node 24.18.0 in every reference header.
Pin framework majors: Express 5, Fastify 5, NestJS 11 - not "latest."
Date the case study: APIs age with dependencies; include 2026-07 context.
Metrics over adjectives: +35% RPS, not "much faster."
Before/after same hardware: Fair throughput comparison.
Load test proof for perf claims: k6 script name or Grafana link.
List deliberate omissions: GraphQL skipped, mesh skipped - scope clarity.
Tenant model explicit: Row-level vs schema-per-tenant in B2B refs.
Worker/API deploy coupling documented: Reference: Worker Fleet.
Idempotency on every side effect: Reference worker standard.
DLQ alert threshold documented: Not "we have a DLQ."
CLI semver and publish channel: Private npm + engines field.
Migration sprint length realistic: Express→Fastify 4 engineer-weeks example.
Breaking changes table: Not prose-only migration pain.
Canary steps recorded: 10→50→100 with guardrails.
Node upgrade waves: Low risk first, native deps last.
CI matrix during LTS transition: 20 + 24 until cutover.
OpenSSL/vendor exceptions with expiry: Not infinite Node 20.
Link motivating ADR: Framework and monolith decisions.
Post-mortem link if incident drove change: Traceability.
Do not copy pool sizes blindly: Scale to your Postgres budget.
Reference != production config: Redact secrets and tenant names.
Review case studies quarterly: Deprecate stale patterns in README.
Use case studies in onboarding week 2: Faster than reading all sections.
Contribute back after adaptation: PR improvements when you learn gaps.
Composite references based on common patterns - not one company's private repo. Validate against your constraints.
After major migration or incident with measurable before/after - store in docs/case-studies/.
Stack versions: This page was written for Node.js 24.18.0 (Active LTS), npm 10+, TypeScript 5.6+, Express 5, Fastify 5, and NestJS 11.
Reviewed by Chris St. John·Last updated Jul 16, 2026