ptalbot:
You can also use Velocity in pool mode to manage that pool of headless workers called by web services - then the web service can return a value
Interesting, I didn’t know Velocity had that. Is there a way to call these asynchronously? Would you still recommend this for large batches of jobs?
Asynchronously because one of our primary uses is to offload a long running process to a server and obviously waiting for a return in that case is non-optimal.
Large batches because a frequently used aspect of my system is to queue up thousands/tens-of-thousands of jobs to run on the server and be sure that even in the even of a catastrophic failure (loss of power, automatic windows update, etc) that all jobs will complete as expected.