Back to Catalog
Integration
Message Construction
Return Address
Tell the receiver where to send the reply — bake the reply address into the request.
Intent & Description
Real-world Use Case
Microservice A sends a validation request to Service B. A includes replyTo=“service-a-replies-queue-us-east-1” in the message header. B validates the payload and sends the result directly to that queue. A picks up the response. No config changes on B needed if A changes its queue name.
Source
📌 TL;DR
Return Address = include your reply queue in the request. Responder sends the answer there. Simple, flexible, and essential for any Request-Reply setup.
Advantages
- Dynamic reply routing — each requester can specify its own reply channel
- Enables multiple requesters to share one responder without reply mix-ups
- No hardcoded reply addresses in the responder
- Standard header in JMS, AMQP, and most broker SDKs
Disadvantages
- Requester must manage its reply channel (creation, cleanup, timeout)
- Adds a field to every request message
- Malformed or missing return addresses cause silent failures
- Requires Correlation Identifier to demux replies on shared channels