NATS Slow Consumer Mitigation about backend-next HOT 3 CLOSED

In my perspective when the producer is faster than the consumer, the buffer will eventually be filled fullly and the only choice is to drop messages. Anyway, just to start a single goroutine to receive messages from NATS and put them to a channel shall solve this. Other than that, we could create a thread pool like panjf2000/ants and then submit consumer tasks to it. This gives the ability to dynamically adjust goroutine count.

Not quite sure whether those work. Not familiar with NATS. :D

from backend-next.

Yes. However the correct behavior is for NATS JetStream to store a reasonable amount of buffer when a slow-consumer is encountered, due to the fact we are not expecting those data to be temporal sequential (delivered in-order). I'll see if there's a way to mitigate this issue as I believe there's some sort of configuration items I could tweak to make it perform better lol.

from backend-next.

wontfix: NATS will not actually drop the message due to the fact we haven't ACKed it, so NATS will send us the "dropped" message just simply later than what we'd expected.

from backend-next.