Implementing At-Least-Once Delivery with NATS JetStream Pull Consumers
Learn how to implement at-least-once delivery guarantees in NATS using JetStream, persistent streams, and Pull Consumers with explicit acknowledgments.
Loading…
ReadMeFeed / Community knowledge
Nats
Real questions. Useful conversations. Find the people who know your stack.
Nats
Developer tools · #nats
Durable Consumers in NATS JetStream for Reliable Event Processing
Use NATS JetStream durable consumers to get at-least-once event processing with replay after crashes, without building your own queue. A named consumer tracks acknowledged sequence so restarts resume safely.
Reliable NATS JetStream Processing With Durable Consumers and Explicit Acks
Use NATS JetStream durable consumers with explicit acknowledgments and file storage to survive crashes without losing in-flight messages, and understand the latency and idempotency trade-offs.
Implementing Reliable Message Processing with NATS JetStream Pull Consumers
Learn how to prevent slow consumer issues in NATS by implementing JetStream Pull Consumers with explicit acknowledgments for reliable, at-least-once delivery.
Durable Consumers in NATS JetStream: State, Replay, and Practical Pitfalls
Durable consumers in JetStream preserve acknowledgment state, enabling seamless restarts and full message replay. Learn how to configure them, avoid common pitfalls, and keep your event‑driven services robust.
Diagnosing Stalled JetStream Pull Consumers: AckPending & Redelivery Issues
When a JetStream pull consumer’s AckPending climbs and messages keep redelivering, the culprit is often AckWait, MaxAckPending, or missing acknowledgments. This guide walks you through spotting the pattern, diagnosing the root cause, and applying targeted fixes to restore smooth delivery.
Implementing Exactly-Once Processing with NATS JetStream Acknowledgment Policies
Learn how to configure NATS JetStream acknowledgment policies and idempotency patterns to achieve exactly-once processing semantics in distributed systems.
Choosing a Moleculer Transporter: NATS, Redis, Kafka, TCP, or MQTT for Production Microservices
A decision guide for selecting a Moleculer transporter (NATS, Redis, Kafka, TCP, MQTT) based on latency, scalability, operational complexity, and feature requirements in production microservice architectures.
Configure NATS JetStream for Durable Message Persistence
Use JetStream streams with file-backed storage and durable, acked consumers to get at-least-once delivery in NATS. This guide shows server config, stream and consumer creation, and how to verify persistence without losing messages on restart.