[Debt] Harden materialization storage and concurrent revision allocation #4

Open
opened 2026-07-28 12:48:19 +02:00 by zemion · 0 comments
Owner

Parent: #1

The first slice intentionally stores bounded rows in JSON and allocates
revisions from the current maximum. Replace those development-scale choices
before large or concurrent production workloads.

Acceptance criteria:

  • transaction-safe monotonic revision allocation under concurrent refresh/promote/freeze
  • durable payload abstraction for database tables, object/file artifacts, and streaming checkpoints
  • no loading of large materializations into process memory for preview or copy
  • checksum and size verification between metadata and payload
  • cleanup/retention remains safe under partial failure
  • PostgreSQL concurrency and failure-injection tests
Parent: https://git.add-ideas.de/GovOPlaN/govoplan-datasources/issues/1 The first slice intentionally stores bounded rows in JSON and allocates revisions from the current maximum. Replace those development-scale choices before large or concurrent production workloads. Acceptance criteria: - transaction-safe monotonic revision allocation under concurrent refresh/promote/freeze - durable payload abstraction for database tables, object/file artifacts, and streaming checkpoints - no loading of large materializations into process memory for preview or copy - checksum and size verification between metadata and payload - cleanup/retention remains safe under partial failure - PostgreSQL concurrency and failure-injection tests
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-datasources#4
No description provided.