Hmmm.
I did read that documentation, but it is still unclear to me:
- a worker does one job at a time? So using one Main and one Worker (queue mode) would automagically queue webhooks?
- the concurrency control is a bit clearer: if I would set that one to “1”, then every webhook is queued if that webhook is running? So the worker can only process a single webhook job at a time?
- What if I have 4 different webhooks and use queue mode. Are those webhooks handled concurrently, or one at a time?
So, there are no possibilities to configure the concurrency of the webhook itself? Some webhooks may run concurrently, and some not.
If you could configure concurrency, one could process multiple webhooks if possible, and (from that flow) post to a “single” webhook where it matters, ie all other concurrent running webhooks will get queued automatically.
The webhooks are fired from Azure EventGrid (there is no node for Azure EventGrid / Blobs / Etc).
I know EventGrid will do retries, but I try to avoid that as the order of events gets mixed up in that case.