What are folks using for job/message queues in #PHP, these days?
Edit: I’m looking for PHP applications or libraries that provide a drop-in job queuing system that your existing code can use to register and manage jobs.
Discussion
Loading...
@ramsey we are quite happy with Symfonys messenger component. They have adapters for most backends. We mostly use RabbitMQ. Our experience is limited to using it in Symfony applications but it should be fully usable without the full framework https://symfony.com/doc/current/components/messenger.html
@ramsey last time I was using BunnyPHP https://github.com/jakubkulhan/bunny with RabbitMQ. The ecommerce system was using the sync version of it, while the workers used ReactPHP and the async Bunny version. I think @wyri is actively working on Bunny lately
@flowcontrol Yes, been working on updating Bunny for its next 0.x release. But given @ramsey's edit I'm not sure @ramsey is looking for Bunny specifically
@ramsey hand-rolled system here built off of SQS and back-end with ReactPHP. Could probably open-source most of it!
@ramsey I praised symfony/messenger so much that I did a whole talk about it last year at #phpday: https://alessandrolai.dev/talks/2024-phpday-symfony-messenger/
It may lose some easiness of configuration when outside of a Symfony app, but it's great and has all the bells and whistles. Also, there are drivers for all kinds of transports, and adapters for drivers from Enqueue too. I even wrote one for MongoDB.
@ramsey
Hi Ben
I'm pretty sure Ecotone, that I use, uses Enqueue:
https://github.com/php-enqueue
@ramsey Right now we have Redis with a custom ReactPHP based layer on top of it, with some really screwy "routing".
@ramsey been using Beanstalkd / Pheanstalk on a recent project, seems solid so far.
@ramsey honestly, with all the libs that exist you can use almost anything, but it depends on your usage. Symfony/messenger give basic interesting stuff, I really enjoy laravel queue because it's simple and the tools around it like horizon are nice. I also heard a lot of good of php-enqueue
@Grummfy I’ve never heard of php-enqueue, but it looks solid, and they use ramsey/uuid, so it must be good! 😉
@ramsey I created a message queue lib that works with MySQL database (and maybe postgres, I don't check), with many interesting features like priority, message to process in future...
That can handle around 100k messages before having some trouble / minor perf issues.
We use it at work without any problem.
https://github.com/php-mqdb/php-mqdb/
That can handle around 100k messages before having some trouble / minor perf issues.
We use it at work without any problem.
https://github.com/php-mqdb/php-mqdb/
Maybe that could correspond to your needs 🙂
@velkuns That’s really cool, but the 100k threshold is problematic. I need something that can handle millions (and not in a hypothetical, future-state way—that’s the volume we already deal with).
@ramsey I understand. Maybe that could not be a problem with MyISAM SQL engine or with postgres, but I can't guarantee that. The only thing is 100k without any problems used in environment with high workload.
I thought you did not need to process millions of messages.
And when I say 100k messages, it 100k messages to waiting to be processed.
I thought you did not need to process millions of messages.
And when I say 100k messages, it 100k messages to waiting to be processed.
System can handle millions of messages over the time, just if we have more than 100k lines in DB, that could affect a little the perf 🙂
@ramsey because Laravel we just use redis and all of Laravel built in stuff, but before that, and also still today if I were not using Laravel, would be beanstalkd and POPOs / JSON with a 100 line worker class. Have probably run billions of jobs through that combo.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled