zlacker

[return to "High-Performance server for NATS.io, the cloud and edge native messaging system"]
1. jitl+dM4[view] [source] 2023-07-23 19:36:20
>>Kinran+(OP)
With all the message queue whatever thingies, as an outside I’m quite confused about ideal use cases.

NATS vs MQTT vs Kafka vs Redis Queue vs Amazon SQS - how do they all stack up?

◧◩
2. Xeoncr+vN4[view] [source] 2023-07-23 19:43:32
>>jitl+dM4
Queues are often used for two reasons: as a way to throttle processing (just throw it into the queue and drain as you have time) and a way to avoid state loss (process the queue item and only ack/clear it once you've done X, Y, & Z. Of course there are more uses, but these are the two most common.

Depending on the throughput you need, the number of clients pulling/putting into the queue, and other things you can rule out certain options. For example, Redis queue will be one of the fastest choices - but is very limited in capacity (memory size). SQS is basically unlimited capacity, but can often have 150ms or more of time elapse between when you put the item in and when it's available.

[go to top]