ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nats
Learn how NATS JetStream's file-based store adds durability to cloud-native messaging with minimal operational overhead, plus configuration tips, performance trade-offs, and verification steps.
A technical guide for choosing between Moleculer transporters (NATS, Redis, TCP, Kafka), comparing their impact on service discovery, RPC latency, and cloud compatibility.
Want to horizontally scale message workers without a load balancer? JetStream pull consumers let you batch‑fetch, ack, and distribute work across workers, giving you flow control and at‑least‑once delivery. Learn how to set up a pull consumer, run workers, and avoid duplicate processing.
How to select and configure a NATS JetStream retention policy (discard=new, discard=old, interest) for a durable event backbone, with operational checks, failure modes, and design pivots.
Set up JetStream durable consumers with explicit acknowledgements so message processing survives crashes — and learn why idempotent handlers are non-negotiable.
Learn how JetStream’s durable subscriptions enable true at‑least‑once delivery, the trade‑offs involved, and a step‑by‑step test you can run today.
When NATS JetStream consumers repeatedly receive the same message, the culprit is often ack timing or consumer configuration. This guide walks through diagnosing redelivery, checking consumer state, and applying fixes such as adjusting ack_wait and max_ack_pending.
JetStream pull consumers let subscribers fetch batches at their own pace with explicit acks, giving you backpressure, at-least-once delivery, and queue-style scaling without extra infrastructure.
A technical decision guide for selecting the right Moleculer transporter. Compare NATS, Redis, JetStream, and AMQP based on durability, latency, and operational cost.
redis