Enterprise Delivery Best Practices

A condensed summary of the 25 most important enterprise delivery practices for Node.js teams - drawn from every page in this section.

Separate PR and release pipelines: PR proves code; release proves image - Delivery Basics.
Tag images with git SHA: Never deploy latest to production.
Expand-contract migrations: Backward-compatible steps enable rollback - Delivery Basics.
Migration before API promote: Run migrate deploy in release pipeline gate.
Document API → worker deploy order: Per service in docs/deploy-order.md.
Pause workers on incompatible schema steps: Avoid poison messages.
Staging mirrors prod pool sizes: Catch pool exhaustion pre-prod.
Smoke test write + read path: /health/ready alone is insufficient.
Feature flags default off: Server-side evaluation - Feature Flags.
Kill switches in runbooks: Flag off before rollback when path is isolated.
Sunset flags after 30 days stable: Stale flags are tech debt.
Canary at 5-10% first: Soak 10+ minutes - Canary & Progressive Delivery.
Guardrail p95 and event-loop lag: Not just 5xx rate.
Auto-rollback on failed analysis: Argo Rollouts or equivalent.
Blue-green keeps warm rollback: Fast swap when canary skipped.
Annotate Grafana with deploys: Correlate incidents in minutes.
Track DORA per service: Frequency, lead time, CFR, MTTR - DORA Metrics for Node Teams.
Tag incidents with deploy SHA: Accurate change failure rate.
Tie deploy speed to error budget: Freeze features when budget low.
Release notes include migration + rollback: Support reads Slack #releases.
CONCURRENTLY indexes on Postgres: Avoid migration locks.
Retain 10 prod image tags: rollout undo requires history.
Worker and API same Node LTS: Runtime skew causes subtle bugs.
Load test after expand migration: Staging with realistic RPS.
Game day rollback quarterly: DORA MTTR is a practiced skill.

FAQs

How fast should Node teams deploy?

As fast as migrations and CFR allow. Daily with flags is common; schema weekly is normal.

Do we need Argo Rollouts?

Any canary with metric analysis works: Spinnaker, Flagger, custom ALB weights.

Delivery Basics - fundamentals
Feature Flags - progressive exposure
Canary & Progressive Delivery - safe promote
DORA Metrics for Node Teams - measurement
CI/CD Best Practices - pipeline depth

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.

Enterprise Delivery Best Practices

A condensed summary of the 25 most important enterprise delivery practices for Node.js teams - drawn from every page in this section.

Separate PR and release pipelines: PR proves code; release proves image - Delivery Basics.

Tag images with git SHA: Never deploy latest to production.

Expand-contract migrations: Backward-compatible steps enable rollback - Delivery Basics.

Migration before API promote: Run migrate deploy in release pipeline gate.

Document API → worker deploy order: Per service in docs/deploy-order.md.

Pause workers on incompatible schema steps: Avoid poison messages.

Staging mirrors prod pool sizes: Catch pool exhaustion pre-prod.

Smoke test write + read path: /health/ready alone is insufficient.

Feature flags default off: Server-side evaluation - Feature Flags.

Kill switches in runbooks: Flag off before rollback when path is isolated.

Sunset flags after 30 days stable: Stale flags are tech debt.

Canary at 5-10% first: Soak 10+ minutes - Canary & Progressive Delivery.

Guardrail p95 and event-loop lag: Not just 5xx rate.

Auto-rollback on failed analysis: Argo Rollouts or equivalent.

Blue-green keeps warm rollback: Fast swap when canary skipped.

Annotate Grafana with deploys: Correlate incidents in minutes.

Track DORA per service: Frequency, lead time, CFR, MTTR - DORA Metrics for Node Teams.

Tag incidents with deploy SHA: Accurate change failure rate.

Tie deploy speed to error budget: Freeze features when budget low.

Release notes include migration + rollback: Support reads Slack #releases.

CONCURRENTLY indexes on Postgres: Avoid migration locks.

Retain 10 prod image tags: rollout undo requires history.

Worker and API same Node LTS: Runtime skew causes subtle bugs.

Load test after expand migration: Staging with realistic RPS.

Game day rollback quarterly: DORA MTTR is a practiced skill.

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.

Enterprise Delivery Best Practices

FAQs

Related

Buscar en la documentación

Enterprise Delivery Best Practices

FAQs

Related