Hacker News Reader

Without more logic than this does this mean any workers that are busy or down mean you lose jobs?

We use a garbage collector to error restart if a job is not served within a specified amount of time.

Great observation, I wrote a little wrongly. What we want ideally is guaranteed delivery to one random free worker. Uuid strategy is better than locking but this could mean that if one worker gets a longer job, all the others on this worker are delayed even if another worker is free.

I think this concept you mentioned would be called sharding? It's kinda required for apache Kafka and others.