Skip to main content

NATS

Solution Approach​

  • Publisher: The Signadot wrapper extracts routing keys from OpenTelemetry baggage headers and injects them into NATS message headers during publishing. Messages are published to the same subjects as before—no routing changes needed.
  • Subscriber: The wrapper intercepts subscription handlers, connects to the Signadot Routes API to determine valid routing keys, and filters messages before passing them to the customer's message handlers. Both baseline and sandbox subscribers use the same subjects.

NATS Architecture Advantages​

Subject-Based Natural Fanout: NATS delivers a copy of each message to all subscribers on a subject. Both baseline and sandbox subscribers receive every message published to their subscribed subjects.

Summary​

  • Use message headers for routing key propagation and filtering.
  • Signadot wrappers automate message filtering for sandbox isolation.
  • No subject or routing changes required; NATS's fanout model ensures all subscribers receive all messages.