The whole value of the bus is that producers and consumers do not know about each other. A receive port publishes a canonical message; each send port declares a subscription — usually a filter over a promoted variable — and the bus delivers a copy to everyone whose filter matches. The producer’s configuration never names a destination.

The anti-pattern is any place where the list of destinations is written into the producer: a component that loops over hard-coded endpoints, or a map that branches on “if partner X also send to Y.” Both turn a routine onboarding into a redeploy and re-couple the very things the bus exists to separate. If routing depends on content, express it as a content-based router — still subscriptions, just smarter filters.