Skip to content

[backend][ops] No graceful DB pool sizing / env-driven configuration #526

Description

@Xhristin3

Severity

Medium

Files

app/backend/src/main.ts, DatabaseModule (or equivalent)

Description

DB pool size, idle timeout, max lifetime, statement timeout are not exposed via env. Staging and production must run with the same defaults, causing cold-start failures under load.

Acceptance Criteria

  • Wire DATABASE_POOL_MIN/MAX, IDLE_TIMEOUT_MS, STATEMENT_TIMEOUT_MS, MAX_LIFETIME_MS via ConfigService
  • Document defaults in docs/ops-tuning.md
  • Add a load-test assertion that pool saturation yields 503 (not 500)

Metadata

Metadata

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions