backgroundjob scalability vs starling

rubyonrails-talk
1

Hi.

I am currently reviewing backgroundjob and starling as alternatives to handling background processing. We would like to architect the system to be scalable. Starling it would seem was designed with scalability in mind, but is more complicated than backgroundjob.

Backgroundjob, from the readme, allows only one worker per hostname, which according to the readme does not affect throughput. It seems significantly simpler to use so I would prefer backgroundjob but I am worried about future scalability.

Does anyone have experience with backgroundjob and scalability?

Regards Ivor

2

Why dont you try the well-known plugin Backgroundrb for handling multiple workers?

http://backgroundrb.rubyforge.org/files/README.html

After you checkout the plugin svn co http://svn.devjavu.com/backgroundrb/trunk

You need to just follow the examples folder... Those examples are pretty easy to understand.

Thats it ! All set to go...

Thanks&Regards, Kiran.

Ivor Paul wrote:

3

Hi Kiran, thanks for the reply.

I am not keen on using backgrounrdrb. I used it in the past and it was a bit of a PITA. I believe that most people suggest backgroundjob above bdrb. My concern is mainly wether backgroundjob will scale as well as starling or if not, how well it will scale.

Regards Ivor