Files
aevolution/docs/adr/0014-message-bus.md
T
dingoandClaude Opus 5 d5b4bd068e Initial commit: architecture docs and headless engineering proof
Aeternalis Evolution, a custom-engine persistent evolutionary MMO.

This first commit establishes the project skeleton:

- Architecture and design docs: project vision, system overview,
  engineering constitution, roadmap, 19 ADRs, and the simulation,
  world, network, persistence and infrastructure architectures.
- Headless engineering proof: deterministic synthetic particles,
  component lifecycle, explicit PRNG streams, canonical snapshots
  and restored execution.
- Build and tooling: CMake 3.28+ / Ninja presets, C++23 feature
  check, clang-format and clang-tidy config, format check script,
  Windows check script, and a Docker build context.
- Tests: unit tests, benchmarks, a snapshot fuzz target and CLI
  integration wiring.

No gameplay, renderer, network service or running deployment yet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-14 15:44:41 -04:00

1.2 KiB
Raw Blame History

ADR-0014: Evaluate NATS JetStream

Status

Proposed for M7–M8 asynchronous integration; no broker in proof.

Context

History/region notifications may need durable fan-out; modular backend can start with direct calls/PostgreSQL.

Decision

Evaluate JetStream first. Publish committed outbox IDs; consumers deduplicate transactionally and ACK after commit. Treat delivery as at least once at application boundary.

Alternatives Considered

PostgreSQL outbox polling avoids service; NATS adds buffering/fan-out; Kafka partition/operations work lacks present evidence; Core NATS alone lacks durable replay.

Benefits

Independent background consumers and backpressure.

Costs

Retention/disk/broker upgrades/credentials/lag operations.

Risks

Duplicate/reordered events, poison records, disk exhaustion, broker-as-truth and same-host replica loss.

Consequences

Test restart/replay/redelivery/retention/poison handling. Required history stays in source of truth. Broker never grants ownership; DB fencing governs writes. Adopt only for measured need. JetStream, server, C client.