Solving Message Loss with NATS JetStream Durable Consumers
Stop losing messages during subscriber downtime. Learn how to implement NATS JetStream durable consumers for guaranteed delivery and state persistence.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop losing messages during subscriber downtime. Learn how to implement NATS JetStream durable consumers for guaranteed delivery and state persistence.
Learn how Moleculer’s Registry automatically finds services and distributes calls using a NATS transporter, plus verification steps and known limits.
Stop losing messages when subscribers go offline. Learn how to use NATS JetStream to implement durable persistence and at-least-once delivery guarantees.
Learn how to implement durable, 'at-least-once' messaging using NATS JetStream, focusing on File storage, Pull consumers, and operational lag monitoring.
Learn how to use NATS JetStream Durable Consumers to move from ephemeral pub-sub to guaranteed at-least-once delivery for critical distributed systems.
How to set max_age and max_bytes on a NATS JetStream file store to bound disk usage and control message retention.
Goal Prevent unauthenticated clients from publishing to any subject while using JetStream’s ACL configuration. Current Constraint The NATS server treats an unauthenticated connection as the special public user. If the ACL file does not contain an explicit deny rule for this user, the default behavior is permissive—any client can publish to any subject. Unres
JetStream Stream Retention Policy Precedence When configuring a JetStream stream with multiple retention limits— MaxBytes , MaxMsgs , and MaxAge —the NATS server accepts the settings without error but does not document a clear rule for which limit is evaluated first during message ingestion. This ambiguity can lead to unexpected eviction behavior, especially
NATS JetStream utilizes the MaxAckPending configuration to limit the number of unacknowledged messages a consumer can have outstanding. This mechanism is critical for preventing consumer saturation and managing resource allocation on the server. When using Pull Consumers with AckExplicit , the client controls the request rate via batch sizes. However, there