I have so far gotten by plenty well writing my own queue systems to fit the needs of the consuming application. Normally the only place where I need queue systems is in distributed systems with rapid fire transmissions to ensure messages hit the network in time sequence order. The additional benefit is that network traffic is saved in order when the current network socket fails so that nothing is lost but time.
I played with most message queues and I go with RabbitMQ in production.
Mostly because it has been very reliable for years in production at a previous company, and doesn’t require babysitting. Its recent versions also has new features that make it is a descent alternative to Kafka if you don’t need to scale to the moon.
I have so far gotten by plenty well writing my own queue systems to fit the needs of the consuming application. Normally the only place where I need queue systems is in distributed systems with rapid fire transmissions to ensure messages hit the network in time sequence order. The additional benefit is that network traffic is saved in order when the current network socket fails so that nothing is lost but time.
I played with most message queues and I go with RabbitMQ in production.
Mostly because it has been very reliable for years in production at a previous company, and doesn’t require babysitting. Its recent versions also has new features that make it is a descent alternative to Kafka if you don’t need to scale to the moon.
And the logo is a rabbit.
A cron job did thd work.
Kafka for communication between microservices, and MQTT (VerneMQ) for IOT devices
What are your thoughts on Apache Pulsar vs Kafka?
I'm hesitating with EMQx, have you tried it? why did you choose VerneMQ?
Sidekiq, Sidekiq, Sidekiq (or just Postgres if Im dealing with something trivial)
SQS. For Ruby apps I use Shoryuken with SQS.
Surprised no body is mentioning ActiveMQ!
Solid queue in rails
NATS