NServiceBus.RabbitMQ icon indicating copy to clipboard operation
NServiceBus.RabbitMQ copied to clipboard

Ability to not have the delayed delivery infrastructure created

Open ramonsmits opened this issue 1 year ago • 0 comments

Describe the feature.

Is your feature related to a problem? Please describe.

Users that do not use saga timeouts, delayed retries or delayed delivery do not require the delayed delivery infrastructure resources created by the transport.

With MSMQ transport delayed delivery is an explicit opt-in but with RabbitMQ no method exists to prevent the creation.

RabbitMQ is (at the moment) the only transport that uses a custom delayed delivery mechanism. Ideally Core could request if it requires delayed delivery from the transport so the transport could decide not to create the delayed delivery infrastructure but as this is really RabbitMQ specific it would make sense to only have a transport API to disable the custom delayed delivery infrastructure.

Describe the requested feature

a. Have an API on the transport to disable the custom delayed infrastructure mechanism thus creating these resources, or b. Have an API on core disable delayed delivery that will be passed to the RabbitMQ transport to prevent creation of the custom delayed infrastructure resources.

Describe alternatives you've considered

See option (B), but as RabbitMQ is the only transport with a custom delayed delivery mechanism it makes sense to drive this effort by modifying Core + Transport and have this issue on this repo.

Additional Context

No response

ramonsmits avatar Jun 29 '23 22:06 ramonsmits