# Messaging Bridge

> Connect two messaging systems together — forward messages across broker boundaries.

- **Category**: Integration
- **Subcategory**: Message Channels
- **Canonical URL**: https://designpattern.fyi/patterns/messaging_bridge/

---

## Description
Clean, reusable architecture pattern.


## Use Cases
M&A integration — acquired company runs RabbitMQ, acquirer runs AWS SNS/SQS. Messaging Bridge forwards OrderPlaced messages from RabbitMQ to SQS. Acquirer''s fulfillment system processes orders from both companies on one channel. Neither messaging system is replaced immediately.





## Trade-offs


### Advantages

- Connects heterogeneous messaging systems without replacing either

- Enables gradual migration between brokers

- Neither side needs to know about the other''s messaging technology

- Transparent from the perspective of producers and consumers on each side




### Considerations & Drawbacks

- Bridge adds latency (an extra hop between systems)

- Bridge is a single point of failure in the cross-system flow — must be HA

- Backpressure management between systems with different throughput profiles is complex

- Duplicate delivery risk if bridge crashes after consuming but before republishing







---
**Reference**: [Original Source](https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessagingBridge.html)