Agreed. In case of having the event dynamically distributed to multiple event queues your way is the best. Just in case one custom event queue would be enough it is easier to use the field “queue” on the registry and skip the fifth parameter in the code. This makes maintenance more efficient and might be easier to use. I just wanted to make sure this was mentioned in the otherwise very informative article.

Hi Christoph! Thanks for reading through the article and commenting. You are right, there is a Queue field that could be used, but if you take a look the code that is generating the events, you’ll notice that it is distributing the same event to N different queues. Using the Queue field instead of the code-driven distribution would mean that we would need N amount events, that will be tied to N different queues.

When the event is triggered “gs.eventQueue(‘event.name’,…” you don’t need to specify the fifth parameter as these events will always go into the queue specified on the “Event Registration”.

Maybe an information that might be added in the article.