- Issue created by @mrconnerton
- π«π·France fgm Paris, France
Just my 0.02: for a number of years now, most clients who used to rely on Beanstalkd have been moving to RabbitMQ, Kafka, or SQS for those on SQS.
For some hard numbers on the module users
Beanstalkd: 26, of which 0 on D8+
RabbitMQ: 133, of which 110 on D8+ (over 800 at one point in 2021 !)
Kafka: 28, 28 of which on D8+
SQS: 204 for the AWS module, all of them on D8+, no details on the use of the AWS services, so SQS is very likely only a portion of that.For all practical purposes, I think Beanstalkd is going the way of the dodo. Which is sad, admittedly.
- πΊπΈUnited States mrconnerton
Awesome, this is exactly the kind of feedback I was looking for and appreciate the quick research. Beanstalkd was always so easy to use and setup to offload the queue from the db, that part of me is still wondering is it worth the effort to take a stab at an updated version with pheanstalk v5. I guess I will have to take a look at the level of effort for RabbitMQ or Kafka as well.
- π«π·France fgm Paris, France
It's simple, really, IMHO:
- Unless you already know you need it, don't even bother with Kafka. If you need it, you'll already know you need it.
- If you're using AWS, SQS is just awesome and works with zero configuration and maintenance. Use it.
- Otherwise, use RabbitMQ
Do not spend time wondering about NATS, NSQ, evQueue, and others.
- Status changed to Closed: works as designed
over 1 year ago 12:44pm 27 July 2023 - Status changed to Fixed
over 1 year ago 1:47pm 27 July 2023 - π«π·France fgm Paris, France
Actually a better status was "Fixed". Thanks for confirming this solved your issue.
What did you end up deciding, BTW ?
Automatically closed - issue fixed for 2 weeks with no activity.