bunjs-docker-mastery（bunjs Docker mastery 部署）

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.

“Bad vs Good” (common production pitfalls)

// ❌ BAD: parsing untrusted input directly in the service layer.
const user = await userService.create(await c.req.json())

// ✅ GOOD: validate at the HTTP boundary before entering business logic.
const payload = c.req.valid("json")
const user = await userService.create(payload)

// ❌ BAD: fire-and-forget async work with no ownership or logging.
void sendWebhook(order)

// ✅ GOOD: await or queue the side effect with explicit failure handling.
await webhookPublisher.publish(order).catch((error) => {
  logger.error({ error, orderId: order.id }, "publish webhook failed")
  throw new AppError("Webhook publish failed", 503, "WEBHOOK_UNAVAILABLE")
})

Recommended Structure

src/
├── index.ts
├── app.ts
├── config/
├── routes/
├── controllers/
├── services/
├── repositories/
├── middlewares/
├── utils/
└── types/

Validation Commands

• Run bun install --frozen-lockfile.
• Run bun run test.
• Run bunx tsc --noEmit if the project uses standalone TypeScript checks.
• Run bunx @biomejs/biome check..
• Run bun run build before release.
• Run Docker build validation for production images when Docker is part of the deliverable.

Runtime and API Guardrails

• Use a single request ID / trace ID strategy and include it in logs and error responses where appropriate.
• Set request body limits, timeouts, and rate limits for public endpoints.
• Do not leak stack traces, secrets, or database errors to clients.
• Prefer Bun.password for password hashing instead of legacy bcrypt stacks unless compatibility requires otherwise.
• Make shutdown explicit: stop accepting traffic, drain in-flight work, and close DB/Redis clients.

Docker & Deployment Defaults

• Use multi-stage Docker builds.
• Run as non-root.
• Pin Bun base image versions; avoid floating latest tags.
• Add /health and /ready endpoints for orchestration environments.
• Keep image contents minimal and deterministic.

Testing Defaults

• Unit tests for pure logic and service policies.
• Integration tests for database repositories and route behavior.
• E2E tests only for critical user flows.
• Keep mocks small and close to the consumer boundary.

References

• Clean code patterns: references/clean-code-patterns.md
• Debugging guide: references/debugging-guide.md
• Docker patterns: references/docker-patterns.md
• Library arsenal: references/library-arsenal.md
• Auth and session security: references/auth-and-session-security.md
• Background jobs and queues: references/background-jobs-and-queues.md
• Database and transactions: references/database-and-transactions.md
• Observability: references/observability.md
• Security and outbound HTTP: references/security-and-outbound-http.md
• Testing strategy: references/testing-strategy.md
• Reliability and operations: references/reliability-and-operations.md

Scripts & Assets

• scripts/init-project.sh - initialize a Bun project from the template.
• scripts/healthcheck.ts - health endpoint template.
• assets/project-template/ - project boilerplate.