Docs / Operations
IMPLEMENTED DOCUMENTED — DEPLOYMENT CONFIGURATION REQUIRED
⏱️ 2 min read · 255 words
Operations
Production is designed as separate API and worker processes.
API service
└─ npm start
Worker service
└─ npm run worker
Shared:
PostgreSQL
Redis
private object storage
Health
GET /api/health reports runtime health from database and queue checks.
Readiness
npm run preflight:production validates production configuration shape/presence without making vendor calls.
Workers
Workers use BullMQ/Redis and are expected to run with:
- bounded retries;
- backoff;
- timeouts;
- leases;
- cancellation;
- dead-letter/replay handling;
- correlation IDs;
- health/metrics.
Migrations
The repository maintains an authoritative migration replay chain and includes verification tooling.
Production distinction
A deployment artifact is not production evidence until it has been deployed and its database, queue, health, backup, restore, monitoring, and rollback behavior have been verified.