A customer running a NATS super-cluster across two regions hit a constraint: they couldn’t import the same subject from two regional accounts into their cross-region account. NATS enforces subject import uniqueness per account – you can’t have two sources for the same subject. The usual workarounds are bad. Region-specific subjects (payments.region1.process) force applications to be region-aware. A central routing proxy adds latency and a single point of failure. Subject mappings solve this c...
No comments yet. Log in to discuss on the Fediverse