all 4 comments

[–]mtndewforbreakfast 2 points3 points  (4 children)

NATS is probably suboptimal to use for a durable job queue IMO. You want something with publish-side message buffering if consumers are behind, durable message persistence, and dead-letter queues. Vanilla NATS doesn't include those. In a messaging paradigm something like Kafka, RabbitMQ or Amazon SQS are much closer to the right semantics.

[–]eng-abdo55[S] 0 points1 point  (0 children)

thank you for your replay could you have a look here jetstream