Решения
Решения
0003 - NATS for service communication
Architecture decision: NATS for service communication
На этой странице
Эта страница ещё не переведена, поэтому показана английская версия.
Date: 2026-05-23
Status: Accepted.
Context
Services need request/reply, event delivery and coordination without operating a separate system for each pattern.
Decision
We chose NATS for request/reply, JetStream event delivery and coordination.
Consequences
NATS is a shared dependency on critical paths. JetStream delivery can repeat, so consumers must handle redelivery. Retention is finite and the bus is not the system of record.