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

Published 20 hours ago • verified publisher icon Particular

(name to be decided) routing topology

Open adamralph opened this issue 8 years ago • 3 comments

Depends on #427.

The current default routing topologies (conventional and direct) have problems that could only solved by breaking wire compatibility. Rather than do that, we will deprecate the current routing topologies and introduce a new one which does not have those problems.

Plan of attack

  • [ ] Introduce new topology, and deprecate the conventional and direct routing topologies
  • [ ] Update docs, including upgrade guide

adamralph avatar Aug 08 '17 15:08 adamralph

Requiring a topology choice has been split off into #427 which means this issue no longer requires a breaking change. It remains on the 5.0.0 milestone for now, but we have the option to deliver it in a later (minor) version instead.

adamralph avatar Sep 05 '17 13:09 adamralph

What is this about? No info at all about this topology. What things are addressed. Is this info present somewhere?

ramonsmits avatar Jun 30 '20 14:06 ramonsmits

Came here from https://github.com/Particular/NServiceBus.RabbitMQ/issues/419 that seems to be an issue about obsoleting topologies that haven't even been replaced yet? Should we really keep https://github.com/Particular/NServiceBus.RabbitMQ/issues/419 open and give users the impression those topologies are already obsolete?

timbussmann avatar Apr 12 '21 14:04 timbussmann