If it works, you should.
Laravel is sitting on top of other solutions like you said. (Supervisord, Apache, nginx, etc) if you built it right and plan for scaling then you will be fine.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Afternoon all,
Just looking for some general discourse on a topic I've stumbled into.
We're working on a huge project for a warehouse sortation system. (Think Amz warehouse). We've got team of people from the guys fitting the conveyor belts and hardware, electricians, through SCADA programmers and a Laravel programmer. We were initially charged with writing the web application to view data fed from a MS-SQL database (A fairly bland CRUD type system). Two other parts of this system were going to be handled by a Windows service - subscribing to an MQTT topic, making some decisions and publishing an answer to a different topic.
Whilst writing some tests, I've realised that Laravel can do this. We've successfully got the two jobs up and running under supervisor and we've run 1000s of successful tests through it. It seems to be quite happy.
I can't help thinking that Laravel wasn't built for controlling industrial hardware however it seems to be perfectly fine doing so. However I can't help thinking that just because it can - it should. (As opposed to some currently unknown Windows service nobody has written yet doing exactly the same thing).
What are other people's thoughts on this? Should we? Shouldn't we?
Please or to participate in this conversation.