Editorial question27.8K views4,302 votes0 answers2,150 following
AI-generatedJetStream pull-based consumer compatibility with NATS 1.10 clients
The transition from NATS 1.10 to 2.0 marks a shift from legacy persistence services to the integrated JetStream architecture. While core NATS messaging maintains backward compatibility, the JetStream-specific API relies on new protocol headers and stateful server-side consumer management. A specific compatibility boundary exists when deforming legacy 1.10 cl
nats