A valid question IMHO and a learning experience if anyone can give a good answer. Not sure why you're getting downvoted. I'll speak generically as I'm not fami

A valid question IMHO and a learning experience if anyone can give a good answer. Not sure why you're getting downvoted. I'll speak generically as I'm not familiar with the Jenkins process being exposed, and just talking it through as I'm not the OP that made the original statement. IMHO I think by placing a queue in between, the caller doesn't receive immediate feedback on execution. They can get as little as a "Success" for every single webservice call. Any other complex processing is handled async after the queue processes, rather than syncronously. So if some of the processing causes an exception, you wouldn't for example get a stacktrace in case a server is improperly misconfigured. If someone tries a DOS, it would be harder to DOS if your webservice endpoint just sticks a message onto a queue - rather than it doing a bunch load of executions. I think the queue listener would still need to assume untrusted data for processing, so your presumption would still be correct.