|
History
|
|
|
Acknowledgements
|
|
|
Podcasts
|
|
|
Notification Form
|
|
|
Feedback Form
|
|
|
Press Release #1
|
|
|
Press Release #2
|
|
|
Press Release #3
|
Master SOA Design
Pattern Catalog
|
|
|
|
Master Pattern List (alphabetical)
|
|
|
Master Pattern List (by category)
|
|
|
Master Pattern List (Text)
|
|
|
Pattern Notation
|
|
|
Pattern Profiles
|
|
|
Symbol Legend
|
|
|
Pattern Contribution Form
|
|
|
SOA Patterns Review Committee
|
|
|
Candidate Patterns Overview
|
|
|
Candidate Patterns List
|
|
|
Candidate Pattern Contribution Form
|
|
|
Candidate Pattern
Feedback Form
|
|
|
SOA Pattern Template
|
|
|
What's a Design Pattern?
|
|
|
What's a Design Pattern Language?
|
|
|
What's a Compound Pattern?
|
|
|
SOA Patterns and Application Technologies
|
|
|
SOA Design Patterns Historical Influences
|
|
|
SOA Design Patterns and Design Principles
|
|
|
SOA Design Patterns and Design Granularity
|
|
|
Legal
|
|
|
Design Patterns Publications
|
|
|
Reference Posters
|
|
|
SOAPrinciples.com
|
|
|
WhatIsSOA.com
|
|
|
SOA Visio Stencil
|
|
|
Reliable Messaging
(Little, Rischbeck, Simon)
|
Home > Service Messaging Patterns > Reliable Messaging
|
|
How can services communicate reliably when implemented in an
unreliable environment?
|
|
|
|
|
|
Problem
Service communication cannot be guaranteed when using
unreliable messaging protocols or when dependent on an
otherwise unreliable environment.
|
|
|
Solution
An intermediate reliability mechanism is introduced into the
inventory architecture, ensuring that message delivery is
guaranteed.
|
|
|
Application
Middleware, service agents, and data stores are deployed to track
message deliveries, manage the issuance of acknowledgements,
and persist messages during failure conditions.
|
|
|
|
Impacts
Using a reliability framework adds processing overhead that can
affect service activity performance. It also increases composition
design complexity and may not be compatible with Atomic
Service Transaction.
|
|
|
|
Principles
Service Composability
|
|
|
|
Architecture
Inventory, Composition
|
|
|
|
| |
|
|
|
When building services as Web services, this pattern is commonly applied by implementing a combination of the WS-ReliableMessaging standard (A) and guaranteed delivery extensions, such as a persistent repository (B). This figure highlights the typical moving parts of the resulting reliability framework.
|
|
|
Audio Podcast
|
|
|
|
This pattern is discussed as part of the audio podcast:
The ESB and Related Messaging Patterns
|
|
|
|
|
Related Patterns in This Catalog
Asynchronous Queuing (Little, Rischbeck, Simon),
Canonical Resources (Erl),
Event-Driven Messaging (Little, Rischbeck, Simon),
Message Metadata (Erl),
Service Agent (Erl),
Service Callback (Karmarkar),
Service Messaging (Erl),
State Messaging (Karmarkar)
|
|
|
|
Related Patterns in Other Catalogs
Guaranteed Delivery (Hohpe, Woolfe)
|
|
|
|
Related Service-Oriented Computing Goals
Increased Vendor
Diversification Options, Reduced IT Burden
|
|
|
This page contains excerpts from:
SOA Design Patterns by Thomas Erl
Foreword by Grady Booch
With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy,
Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.
(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)
For more information about this book, visit www.soabooks.com.
|
|