Send a request with enough metadata to identify where and how to respond.
System Management
Smart Proxy
Place a proxy between requestor and service that records correlation state, forwards requests and rewrites replies so the original interaction remains traceable.
How can you track messages on a service that publishes reply messages to the Return Address specified by the requestor?Adapted from Enterprise Integration Patterns under CC BY 3.0. The visualization and explanatory content on this page are original GateSift material.
Original GateSift visualization
How Smart Proxy works
A request and its response are connected even when messaging is asynchronous.
Request
Smart Proxy
Reply
Apply Smart Proxy to preserve the reply path or correlation context.
Return the response to the correct requester and match it to the original request.
What this pattern helps you decide
Place a proxy between requestor and service that records correlation state, forwards requests and rewrites replies so the original interaction remains traceable.
What happens when processing fails or the same message is delivered twice?
Where does state, correlation or routing configuration live?
How will operators trace the message and understand the decision path?
Where you may see it
- API gateway correlation proxy
- Service Bus reply proxy
- BizTalk intermediary orchestration
How the analyzers can surface it
- Proxy and correlation behavior
- Return-address rewriting
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
Source, licence and attribution
The pattern name and selected problem statement are adapted from Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf under CC BY 3.0. GateSift summaries, Azure mappings, analyzer guidance and diagrams are original. No endorsement by the original authors is implied.