search

Particular / NServiceBus

Build, version, and monitor better microservices with the most powerful service platform for .NET
https://particular.net/nservicebus/
Other
2.07k stars 647 forks source link

Satellite queue naming #4451

Open SeanFeldman opened 7 years ago

SeanFeldman commented 7 years ago

While reviewing a bug fix for https://github.com/Particular/NServiceBus.AzureServiceBus/issues/480 for ASB, have noticed that in order to create a custom satellite, we don't allow an easy way to follow NSB convention for satellite naming.

Our satellite registration API (sample) expects a transport address. It doesn't allow to pass in a qualifier and let the FW handle the transport address construction. Should one want to follow the convention, they'd need to know the "procedure" to turn a qualifier into a transport address.

Should we provide an overload that takes a satellite qualifier and generates a transport address using NSB satellite conventions w/o burden of the conversion mentioned above?

SeanFeldman commented 7 years ago

cc @bording

timbussmann commented 7 years ago

yeah, the whole endpoint address stuff is a nightmare (also for routing). The qualifier idea would definitely work, maybe this is a reasonable enough workaround but I'd prefer to fix this once for all.

andreasohlund commented 7 years ago

Me and @timbussmann decided to park this on the future milestone for now since there is a workaround and we have other more pressing issues atm

timbussmann commented 7 years ago

btw. this is related imho: https://github.com/Particular/NServiceBus/issues/4111