'Laravel Queues vs Kafka/RabbitMQ

At our company we currently sending around 1.5 to 2 million text messages per month using various services like Ring Ring, Nexmo, Twilio, ... This is currently done by some old cronjob script we wrote 10 years ago. We are finally about to rewrite the complete structure and start using queues instead. We are trying to decide whether to use the build-in Laravel Queues (Redis) or a full-blown messaging queue like Apache Kafka or RabbitMQ. We currently tend to just use Laravel Queues as we already have experience with these for sending some emails and webhooks (not at a 2-3 million per month scale). Things like Laravel Horizon and the easy configurability of the queues is also an advantage.

Does anyone have experience with running 2-3 million jobs a month using Laravel Queues? I don't think this will be an issue performance wise. I am currently not seeing and reason to use Kafka/RabbitMQ over the built-in Laravel Queues tbf. Am I missing something or are there any potential problems we can run into when using Laravel Queues? Any concerns or general advise, let me know.

Thanks in advance.



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source