Post

For the #laravel crew on here, do you typically just use standard Laravel queues backed by the DB, or Horizon (Redis backed)?

0 reposts2 likes

When running on AWS I used SQS Super cheap and lots of logging Used a queue per service so one thing didn't hold up another and with vapour , workers would devour the jobs

Yes - cloudwatch has lots of nice charts to see how many jobs are being added and processed so it can be quick to spot if your jobs aren't being processed.

Nice. Do you ever use the pause/continue stuff that Horizon offers, or just good with the general observability? And, have you ever ran into issues with the size or your Redis instance, or need to scale up/wish you could scale down?

Yes; as part of forge deployment - pausing horizon before i start (some of apps are older and do not support zero-downtime deployment) And I did run into redis bloating out of control; but it was my fault, not redis'

Yeah, that makes sense. With your DB-backed queues, do you ever wish you had some of the control that Horizon offers, like being able to pause and continue processors, or being able to clean failed jobs/clear jobs from the queue?

With your DB-backed queues, do you ever wish you had some of the control that Horizon offers, like being able to pause and continue processors, or being able to clean failed jobs/clear jobs from the queue? Or, just generally check-in and make sure the queue is running properly and jobs are fast?