|
|
|
|
|
|
by jrochkind1
817 days ago
|
|
|
if you have very high volume, there can be some tricks to using an rdbms as a queue system. For Rails use, 37Signals recently released the open source solid queue package, meant for use with either msyql or postgres. It makes some odd choices, like separating things into different tables depending on state. And it also makes careful use of the not-necessarily-super-well-known (but standard, and in both mysql and postgres) `FOR UPDATE SKIP LOCKED` clause. These choices were to get good performance at high volumes, which they think they have done and tested. So it can be done! Probably. And indeed solid queue is MIT-licensed, there are not barriers to looking at the choices they made and copying them in whatever language/platform you want. But it's not necessarily trivial. At non-huge volumes though it's probably not an issue. https://github.com/rails/solid_queue |
|
|