Request-Reply

Async messaging that still needs an answer.

• Format.puml
• Length29 lines
• LibraryEnterprise Integration Patterns

The source

29 lines of PlantUML, and pulls in Enterprise Integration Patterns. Copy it, or open the template inside Gnomon and render it as it is.

@startuml
!include https://raw.githubusercontent.com/plantuml-stdlib/EIP-PlantUML/main/dist/EIP-PlantUML.puml

title Request-Reply Pattern

MessagingGateway(client, "Client Application")

P2PChannel(requestChannel, "Request Channel")
P2PChannel(replyChannel, "Reply Channel")

ServiceActivator(service, "Order Service")

RequestReply(request, "Order Request")
Message(reply, "Order Response")

Send(client, request)
Send(request, requestChannel)
Send(requestChannel, service)
Send(service, reply)
Send(reply, replyChannel)
Send(replyChannel, client)

note right of request
  Contains:
  - Return Address
  - Correlation ID
end note

@enduml

Others in Enterprise integration pattern diagrams

• Simple MessagingA channel and two endpoints: the vocabulary in miniature.
• Content-Based RouterRoute by message content. Where most integrations start.
• Publish-SubscribeOne publisher, many independent subscribers.
• Splitter-AggregatorSplit a message, process the parts, put them back together.
• Pipes and FiltersA processing chain where each stage is replaceable.
• Error HandlingWhat happens when a message cannot be processed. Draw this one.
• Wire Tap (Monitoring)Observe traffic without changing it: for audit and monitoring.