SOA Patterns > Service Messaging Patterns > Service Callback
Service Callback (Service Messaging Patterns)
How can a service communicate asynchronously with its consumers?
Problem
When a service needs to respond to a consumer request through the issuance of multiple messages or when service message processing requires a large amount of time, it is often not possible to communicate synchronously.
Solution
A service can require that consumers communicate with it asynchronously and provide a callback address to which the service can send response messages.
Application
A callback address generation and message correlation mechanism needs to be incorporated into the messaging framework and the overall inventory architecture.
Impacts
Asynchronous communication can introduce reliability concerns and can further require that surrounding infrastructure be upgraded to fully support the necessary callback correlation.
Architecture
Inventory, Service, Composition
Service A sends a message containing the callback address and correlation information to Service B (1). While Service B is processing the message, Service A is unblocked (2). Service B, at some later point in time, sends a response containing the correlation information to the callback address to Service A (3). While Service B retains this callback address, it can continue to issue subsequent response messages to Service A.
Related Patterns in This Catalog
Asynchronous Queuing, Atomic Service Transaction, Event-Driven Messaging, File Gateway, Messaging Metadata, Reliable Messaging, Service Agent
Related Patterns in Other Catalogs
Correlation Identifier,
Return Address
Related Service-Oriented Computing Goals
This page contains excerpts from:
SOA Design Patterns by Thomas Erl
(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)
For more information about this book, visit www.arcitura.com/books.