3 ms·
It's true, message buses and work queues have different characteristics. It sounds like you want a work queue, not a message bus. I have very successful experie
by ketralnis 6y ago
It's true, message buses and work queues have different characteristics. It sounds like you want a work queue, not a message bus. I have very successful experience with using rabbitmq for work queueing, but as you mention there are others too.
- biggestlou 6y agoPulsar works quite well as a message queue: https://pulsar.apache.org/docs/en/cookbooks-message-queue/ https://pulsar.apache.org/docs/en/cookbooks-message-queue/
- skyde 6y agoPulsar can also support infinite data retention using data tiering and by spreading data on all nodes. It’s much better than Kafka when you don’t know when the consumer will come back looking for what changed
- biggestlou 6y agoSpreading data on all BookKeeper nodes, yes :) Pulsar brokers are themselves stateless.
- gnfargbl 6y agoYou’re right. The issue is that in this particular application I need _both_ a work queue and a message bus. I’ve also successfully used Rabbit as a work queue, but it’s not high-throughput enough to meet my messaging needs. Pulsar seems to cope well in both roles. All that said, if I had my time again I’d probably just use one of the cloud providers’ solutions and spend my efforts elsewhere...