News for hackers. Stuff that matters.
Re:Show HN: Sneakers – Fast background processing for Ruby by zimbatm on Tuesday January 07, 2014 @05:56PM (#7020594)
It doesn't hurt to keep a higher-level job representation in DB and sync the state at each step of the processing. I don't know about sneakers but you might want to have more states than the usual new/processing/success|fail.

Obviously it really depends on what you're doing, if the jobs are re-entrant, if they're the fire-and-forget kind of types, ... Still in most of the cases I would just store the jobs as a table entry and pass the table+id to the job processor. Even if PostgreSQL was the primary data store for the job processor there would still be issues with external state that needs to be healed when restoring from backup.

There are no comments on this comment yet.