views:

59

answers:

2

I need to build an internal service that queues the DB for changes (in one table) every one second, and processed data after this event.

I do not need all the Rails stack since this service does not need the Controller/View functionality. Basically, from the rails stack, i only need AR (or an ORM).

The found solutions/approaches for this are:

  • Use a classic rails background processing plugin (like starling/workling, delayed_job, etc)
  • Use a daemon solution like RAA Daemons(and maybe as ORM, use DataMapper, since it can be used stand-alone)
  • Redesign things and use an MQ sollution

What would you suggest it would be the best approach?

+1  A: 

How about a solution like RabbitMQ ?

marcgg
+1  A: 

Instead of using Rails, you can simply download ActiveRecord here and include it as a library. That way you have the ORM you like, without the overhead of the Rails stack.

As far as the Ruby "Controller" portion of it goes, you can use whatever daemon solution you like.

Mike Trpcic