Support the ongoing development of Laravel.io →
Queues Architecture

I'm using Laravel queue system for the first time and I have some questions about the architecture :

The queue listener runs as a daemon , what's the benefits of this approach against a frequent cron job ?

As a test , I created a Queue::push which logs some string with Log::info and saw that 3-5 logs are added per second. What should I do to run parallel queues? Another approach is to do more on each Queue::push ( for example a loop for multiple logs in this example ) the problem of this approach is that it can't be used in some cases (for example when a user sings up and a confirmation email is sent to him). What should be done in these situations?

Last updated 2 years ago.
0

Sign in to participate in this thread!

Eventy

Your banner here too?

reshadman reshadman Joined 15 Feb 2014

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2025 Laravel.io - All rights reserved.