Good post. It should be added that RabbitMQ does Priority Queuing for messages with MQTT, thought the priority values are confined to 0-255 (which generally is more than enough) so enrichment queues are a great benefit.
If I remember correctly, the drawback from streams is that they don't stop collecting data. In many use cases outside of big companies they would be overkill and over complicated. I also don't believe you have dead-letter queues like you would in Rabbit/MQTT.
I'm partial to Rabbit since every time I have to deal with apache it adds a lot of complications. I try to stay away from anything amazon related. I don't trust anything out of Washington State.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good post. It should be added that RabbitMQ does Priority Queuing for messages with MQTT, thought the priority values are confined to 0-255 (which generally is more than enough) so enrichment queues are a great benefit.
If I remember correctly, the drawback from streams is that they don't stop collecting data. In many use cases outside of big companies they would be overkill and over complicated. I also don't believe you have dead-letter queues like you would in Rabbit/MQTT.
I'm partial to Rabbit since every time I have to deal with apache it adds a lot of complications. I try to stay away from anything amazon related. I don't trust anything out of Washington State.