Is there much difference between using Beanstalkd and a database driver for queues?
What would some pros and cons be? The database queue seems to easier to setup and run, what should I know about using it?
Theres no real explanations in the docs about it.
Using a database as a queue can be simpler to setup and probably easier to test on a development machine. But running a database as a queue in production may not be a very good idea; especially in a high traffic scenario. Although a database may not be the right tool for queueing, let's look at the pros & cons of using it as such.
Pros:
Cons:
Messaging queues such as SQS, Beanstalkd, RabbitMQ etc. are built to handle these scenarios. Since they only care about a message being stored and processed, they don't have to worry about locking and transaction logging (which is required by a database). Adding a messaging queue to your system will help it scale much more easily. Also, it'll let the database breathe by allowing it to do actual transaction processing without worrying about messaging as well.
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments