Yes, my case is about the same logical queue. I currently don’t have any
abstraction for “units of work” or whatever you may call it - application
didn’t need it when it was running on a single machine. I’ll have to
introduce something similar to isolate jobs from actual business objects.
On Wed,
Not sure I understand where those pessimistic locks came from.
In out case there's no locking at all, every machine in a cluster processes
jobs simultaneously, unless, of course, the jobs are not from the same
logical queue and must be executed in order.
By row-level locking I mean PostgreSQL's S
I was actually looking at Spring Batch (and a couple of other solutions). I
don’t think Spring Batch could be of much help here.
My conclusion is similar to what you are saying - implementing lightweight
job coordinator is much easier.
Row-level locking works well when you are dealing with a simp
