Bun.js + Docker Mastery

Operate

• Confirm the goal, scope, Bun version, deployment target, Docker constraints, database choice, traffic profile, and definition of done.
• Prefer small vertical slices with tests and explicit tradeoffs.
• Use Bun-native capabilities when they simplify the system, but do not force Bun-specific APIs where the standard Web platform is already clear.
• Optimize for operability: graceful shutdown, structured logs, health checks, timeouts, and safe defaults are part of the baseline.

The goal is not just “fast on benchmarks”. The goal is a service that stays easy to debug and safe to run in production.

Default Standards

• Keep src/index.ts as bootstrap only; move app wiring to src/app.ts and business logic to services/use-cases.
• Validate environment variables and request payloads at the boundary.
• Prefer explicit error types and one global error mapping strategy.
• Keep TypeScript strict; avoid any, hidden type assertions, and implicit runtime contracts.
• Prefer idempotent handlers for side-effecting endpoints where retries can happen.
• Treat database, cache, and outbound HTTP as failure-prone dependencies: always define timeouts and degradation behavior.