Skip to content

Commit a09ea2d

Browse files
authored
Merge pull request #127926 from Particular/main
Add bridging section for other messaging systems
2 parents 3e0915a + 0f2dccb commit a09ea2d

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

articles/service-bus-messaging/service-bus-integrate-with-rabbitmq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,10 @@ By following the previous steps, you integrated areas of your org that were outs
129129

130130
In the end, messaging is about enabling connections, and with this technique we just opened a new one.
131131

132+
## Advanced scenarios
133+
134+
If you need support for patterns like [request-reply](/azure/architecture/patterns/async-request-reply), whether that is initiated by the RabbitMQ side and replied from the Azure Service Bus side, or vice-versa, then more advanced tooling is needed. The [NServiceBus Messaging Bridge](https://docs.particular.net/nservicebus/bridge/) offers support for request-reply as well as [publish-subscribe](/azure/architecture/patterns/publisher-subscriber), across multiple other message broker technologies.
135+
132136
## Next steps
133137

134138
- Learn more about [Azure Service Bus](./service-bus-messaging-overview.md)

0 commit comments

Comments
 (0)