a queue is a queue - what is your beanstalkd doing that a SQS cant do?
its your server thats the limitation.. ie how slow/fast it is.. any queue will be able to handle lots of data coming through
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I'm currently building a server architecture with a freelancer and we are looking at setting up SQS for my website to handle queues.
Right now we use beanstalkd on our old Digital Ocean server, though when looking at SQS it seems like it is really basic and doesnt really work as beanstalkd does?
Our jobs on our website handles importing data, so a user could for example click "Import" and it does a lot of requests to different APIs and grabs data and puts them into the database, we have around 1000 users online at all times and there are imports running 24/7.
What is recommended for this? Should I stay with using a local beanstalkd on the EC2 server or should I setup SQS?
Is there anything else I can use?
Please or to participate in this conversation.