-
released this
2026-08-05 16:00:31 +00:00 | -3 commits to main since this releasev0.4 Phase 2 — Messaging Domain (P2)
Author the
domains/messaging/tree: 10 first principles + 4 derived docs. Messaging owns the cross-process / network-failure-model angle (D-062): messages as contracts, explicit delivery semantics, idempotent consumers, bounded backpressure, observable lag.Files
domains/messaging/first-principles.md— 10 P-rules (P1 Contracts, P2 Ordering, P3 Idempotent Consumers, P4 Explicit Delivery Semantics, P5 Dead-Letter Handling, P6 Bounded Backpressure, P7 Intentional Partitioning, P8 Replay/Retention, P9 Compatible Schema Evolution, P10 Observable Messaging); traces to 7 core C-rules (C1, C2, C4, C5, C6, C7, C8)domains/messaging/queues.md— at-least-once/at-most-once/exactly-once comparison table (D-069)domains/messaging/pubsub.md— fan-out + shared vs independent subscriptionsdomains/messaging/streams.md— Kafka/Kinesis/Pulsar/NATS JetStream comparison (D-069) + consumer-group rebalance strategies (IDEATE-41)domains/messaging/delivery-semantics.md— dead-letter strategy comparison (D-069) + fenced idempotency-key dedup-store example (IDEATE-39)
Requirements covered
- ATELIER-97, ATELIER-98, ATELIER-99, ATELIER-100, ATELIER-101 (5/5)
Boundary
- D-062: messaging owns cross-process/network-failure-model; concurrency owns in-process/crash-failure-model. No duplication.
- Edge↔messaging bidirectionality resolved: edge/iot.md → messaging/queues link (P1) now resolves.
Next
- P3: Language-derived extension (16 derived docs) -> v0.3.3
Downloads