[Feature] Scalability profiles and autoscaling readiness #217

Closed
opened 2026-07-07 21:16:17 +02:00 by zemion · 3 comments
Owner

Define how GovOPlaN scales from manual single-node deployments to larger deployments with separately scalable web, API, worker, database, storage, queue, cache, and monitoring components.

Source: docs/GOVERNMENT_OPERATIONS_VISION.md

Acceptance criteria:

  • document manual scaling topology first
  • define what must be stateless and what cannot be replicated blindly
  • identify required health/readiness checks and degraded modes
  • define queue/worker scaling assumptions for mail, workflow, transformations, notifications, and reporting
  • identify the PostgreSQL production path and any SQLite-only limits
  • outline autoscaling signals and limits for supported deployment targets
Define how GovOPlaN scales from manual single-node deployments to larger deployments with separately scalable web, API, worker, database, storage, queue, cache, and monitoring components. Source: `docs/GOVERNMENT_OPERATIONS_VISION.md` Acceptance criteria: - document manual scaling topology first - define what must be stateless and what cannot be replicated blindly - identify required health/readiness checks and degraded modes - define queue/worker scaling assumptions for mail, workflow, transformations, notifications, and reporting - identify the PostgreSQL production path and any SQLite-only limits - outline autoscaling signals and limits for supported deployment targets
zemion added the
module/core
label 2026-07-07 23:40:50 +02:00
zemion added the
priority
p2
status
triage
labels 2026-07-08 02:10:00 +02:00
Author
Owner

Codex State: progress

Summary

  • Added the first scalability/readiness design document with deployment profiles, stateless/stateful boundaries, degraded modes, and worker scaling assumptions. Runtime profile selection/autoscaling hooks still remain implementation work.

Changed Files

  • docs/SCALABILITY_AND_SIZING.md

Next / Blocked

  • Runtime/API implementation remains follow-up work.
## Codex State: progress ### Summary - Added the first scalability/readiness design document with deployment profiles, stateless/stateful boundaries, degraded modes, and worker scaling assumptions. Runtime profile selection/autoscaling hooks still remain implementation work. ### Changed Files - `docs/SCALABILITY_AND_SIZING.md` ### Next / Blocked - Runtime/API implementation remains follow-up work.
Author
Owner

Codex Progress Update

The PostgreSQL production path is now identified and exercised by the default dev runtime, which removes one blocker for scalability profile work.

Still open:

  • manual scaling topology
  • stateless/stateful split documentation
  • health/readiness checks and degraded modes
  • queue/worker scaling assumptions
  • autoscaling signals and limits
## Codex Progress Update The PostgreSQL production path is now identified and exercised by the default dev runtime, which removes one blocker for scalability profile work. Still open: - manual scaling topology - stateless/stateful split documentation - health/readiness checks and degraded modes - queue/worker scaling assumptions - autoscaling signals and limits
Author
Owner

Codex State: done

Summary

  • Added/expanded scalability profile documentation with manual-first topology, stateless/stateful boundaries, readiness/degraded modes, worker queue assumptions, PostgreSQL production path, autoscaling signals, and limits.
  • Added production-like dev/ops readiness surfaces earlier in the batch, including Redis, worker, storage, maintenance, and readiness blockers.

Changed Files

  • docs/SCALABILITY_AND_SIZING.md
  • govoplan-ops/docs/SCALABILITY_PROFILES.md
  • govoplan-ops/src/govoplan_ops/backend/api/v1/routes.py
  • govoplan-ops/webui/src/features/ops/OpsPage.tsx

Verification

  • pytest ... test_docs_context_and_ops_status_are_available ... passed in focused set.
  • npm run build in core WebUI passed.
  • git diff --check on touched paths passed.
## Codex State: done ### Summary - Added/expanded scalability profile documentation with manual-first topology, stateless/stateful boundaries, readiness/degraded modes, worker queue assumptions, PostgreSQL production path, autoscaling signals, and limits. - Added production-like dev/ops readiness surfaces earlier in the batch, including Redis, worker, storage, maintenance, and readiness blockers. ### Changed Files - `docs/SCALABILITY_AND_SIZING.md` - `govoplan-ops/docs/SCALABILITY_PROFILES.md` - `govoplan-ops/src/govoplan_ops/backend/api/v1/routes.py` - `govoplan-ops/webui/src/features/ops/OpsPage.tsx` ### Verification - `pytest ... test_docs_context_and_ops_status_are_available ...` passed in focused set. - `npm run build` in core WebUI passed. - `git diff --check` on touched paths passed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#217
No description provided.