How can wrapper services with non-standard contracts be prevented
from spreading indirect consumer-to-implementation coupling?
Problem
Wrapper services required to encapsulate legacy logic are often
forced to introduce a non-standard service contract with high
technology coupling requirements, resulting in a proliferation of
implementation coupling throughout all service consumer
programs.
Solution
The non-standard wrapper service can be replaced by or further
wrapped with a standardized service contract that extracts,
encapsulates, and possibly eliminates legacy technical details
from the contract.
Application
A custom service contract and required service logic need to be
developed to represent the proprietary legacy interface.
Impacts
The introduction of an additional service adds a layer of
processing and associated performance overhead.
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, visitwww.soabooks.com.
Arcitura IT Certified Professionals (AITCP)
Arcitura IT Certified Professionals (AITCP)
Arcitura IT Certified Professionals (AITCP)
Arcitura YouTube Channel
This page contains excerpts from:
