Files
aevolution/docs/adr/0018-infrastructure-services.md
T
2026-10-08 12:08:53 -04:00

36 lines
1.2 KiB
Markdown

[Reviewed]
# ADR-0018: Initial infrastructure services
## Status
Proposed; M0 deploys no services.
## Context
One host constrains resource/operations budgets; adding nodes must increase capacity without game redesign.
## Decision
Modular backend plus disposable region workers, preferred PostgreSQL, S3 adapter, conditional JetStream, no Redis initially. Separate dev/stage/world0 identities, credentials and guarded promotion.
## Alternatives Considered
DB outbox polling can suffice; Kafka needs demonstrated scale; distributed storage requires actual hardware/operational evidence; noun-per-service rejected.
## Benefits
Fewer failure modes, separable adapters and scale by workload.
## Costs
Explicit retention, resource budgets, restore, consumer deduplication and guard tests.
## Risks
Shared-host loss, logs/queue growth, stale storage ownership and accidental deletion.
## Consequences
Pin release digests/licenses; test restoration and limits before M8. JetStream is not DB exactly-once side effects. Official MinIO repo archived April25 2026/no longer maintained: do not adopt archived distribution by default; evaluate maintained S3 backend. [MinIO](https://github.com/minio/minio), [JetStream](https://docs.nats.io/concepts/jetstream).