Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Right now I have a single web server where my laravel app is running.
Due to a increase of request I'm considering the opportunity to scale horizontal, introducing one (or more in future) web server machine.
I've already planned how to manage the updates and so on, but I'm now facing the problem about how to manage queues.
The only solution came up in my mind is to add a small machine to handle just the queue.
What are the best practices in a situation like mine?
Thanks!
Yes, for Load Balancing architecture, that is the way. Have multiple "App Servers", multiple/one "Load Balancer", separate server for "Database", "Redis", "Queue Worker" etc.
Learn more:
Load Balancing: https://serversforhackers.com/s/load-balancing-with-nginx
Managing Persistence: https://serversforhackers.com/c/nginx-lb-managing-persistence
@Niush Thanks for your suggestions. I'll take a look to the links you provide.
Of course the "queue worker" server can be one of the "web server". Correct? (just to know)
@giagara Yes you could. If there won't be much Queue Jobs to run, then, instead of having Idle server sitting around, it can be one (or all) of the app server.
Please or to participate in this conversation.