SOA Design Patterns

E-book Engels 2008 9780138158194
Verwachte levertijd ongeveer 9 werkdagen

Samenvatting

“SOA Design Patterns is an important contribution to the literature and practice
of building and delivering quality software-intensive systems.”

- Grady Booch, IBM Fellow

“With the continued explosion of services and the increased rate of adoption of SOA through the market, there is a critical need for comprehensive, actionable guidance that provides the fastest possible time to results. Microsoft is honored to contribute to the SOA Design Patterns book, and to continue working with the community to realize the value of Real World SOA.”

- Steven Martin, Senior Director, Developer Platform Product Management, Microsoft

 

“SOA Design Patterns provides the proper guidance with the right level of abstraction to be adapted to each organization’s needs, and Oracle is pleased to have contributed to the patterns contained in this book.”

- Dr. Mohamad Afshar, Director of Product Management, Oracle Fusion Middleware, Oracle

 

“Red Hat is pleased to be involved in the SOA Design Patterns book and contribute important SOA design patterns to the community that we and our customers have used within our own SOA platforms. I am sure this will be a great resource for future SOA practitioners.”

- Pierre Fricke Director, Product Line Management, JBoss SOA Platform, Red Hat

 

“A wealth of proven, reusable SOA design patterns, clearly explained and illustrated with examples. An invaluable resource for all those involved in the design of service-oriented solutions.”

- Phil Thomas, Consulting IT Specialist, IBM Software Group

 

“This obligatory almanac of SOA design patterns will become the foundation on which many organizations will build their successful SOA solutions. It will allow organizations to build their own focused SOA design patterns catalog in an expedited fashion knowing that it contains the wealth and expertise of proven SOA best practices.”

- Stephen Bennett, Director, Technology Business Unit, Oracle Corporation

 

“The technical differences between service orientation and object orientation are subtle

enough to confuse even the most advanced developers. Thomas Erl’s book provides a great service by clearly articulating SOA design patterns and differentiating them from similar OO design patterns.”

- Anne Thomas Manes, VP & Research Director, Burton Group

 

“SOA Design Patterns does an excellent job of laying out and discussing the areas of SOA design that a competent SOA practitioner should understand and employ.”

- Robert Laird, SOA Architect, IBM

 

“As always, Thomas delivers again. In a well-structured and easy-to-understand way, this book provides a wonderful collection of patterns each addressing a typical set of SOA design problems with well articulated solutions. The plain language and hundreds of diagrams included in the book help make the complicated subjects of SOA design comprehensible even to those who are new to the SOA design world. It’s a must-have reference book for all SOA practitioners, especially for enterprise architects, solution architects, developers, managers, and business process experts.”

- Canyang Kevin Liu, Solution Architecture Manager, SAP

 

“The concept of service oriented architecture has long promised visions of agile organizations being able to swap out interfaces and applications as business needs change. SOA also promises incredible developer and IT productivity, with the idea that key services would be candidates for cross-enterprise sharing or reuse. But many organizations’ efforts to move to SOA have been mired–by organizational issues, by conflicting vendor messages, and by architectures that may amount to little more than Just a Bunch of Web Services. There’s been a lot of confusion in the SOA marketplace about exactly what SOA is, what it’s supposed to accomplish, and how an enterprise goes about in making it work.

 

SOA Design Patterns is a definitive work that offers clarity on the purpose and functioning of service oriented architecture. SOA Design Patterns not only helps the IT practitioner lay the groundwork for a well-functioning SOA effort across the enterprise, but also connects the dots between SOA and the business requirements in a very concrete way. Plus, this book is completely technology agnostic—SOA Design Patterns rightly focuses on infrastructure and architecture, and it doesn’t matter whether you’re using components of one kind or another, or Java, or .NET, or Web services, or REST-style interfaces.

 

While no two SOA implementations are alike, Thomas Erl and his team of contributors have effectively identified the similarities in composition services need to have at a sub-atomic level in order to interact with each other as we hope they will. The book identifies 85 SOA design patterns which have been developed and thoroughly vetted to ensure that a service-oriented architecture does achieve the flexibility and loose coupling promised. The book is also compelling in that it is a living document, if you will, inviting participation in an open process to identify and formulate new patterns to this growing body of knowledge.”

- Joe McKendrick, Independent Analyst, Author of ZDNet’s SOA Blog

 

“If you want to truly educate yourself on SOA, read this book.”

- Sona Srinivasan, Global Client Services & Operations, CISCO

 

“An impressive decomposition of the process and architectural elements that support serviceoriented analysis, design, and delivery. Right-sized and terminologically consistent.

 

Overall, the book represents a patient separation of concerns in respect of the process and architectural parts that underpin any serious SOA undertaking. Two things stand out. First, the pattern relationship diagrams provide rich views into the systemic relationships that structure a service-oriented architecture: these patterns are not discrete, isolated templates to be applied mechanically to the problem space; rather, they form a network of forces and constraints that guide the practitioner to consider the task at hand in the context of its inter-dependencies. Second, the pattern sequence diagrams and accompanying notes provide a useful framework for planning and executing the many activities that comprise an SOA engagement.”

- Ian Robinson, Principal Technology Consultant, ThoughtWorks

 

“Successful implementation of SOA principles requires a shift in focus from software system means, or the way capabilities are developed, to the desired end results, or real-world effects required to satisfy organizational business processes. In SOA Design Patterns, Thomas Erl provides service architects with a broad palette of reusable service patterns that describe service capabilities that can cut across many SOA applications. Service architects taking advantage of these patterns will save a great deal of time describing and assembling services to deliver the real world effects they need to meet their organization’s specific business objectives.”

- Chuck Georgo, Public Safety and National Security Architect

 

“In IT, we have increasingly come to see the value of having catalogs of good solution patterns in programming and systems design. With this book, Thomas Erl brings a comprehensive set of patterns to bear on the world of SOA. These patterns enable easily communicated, reusable, and effective solutions, allowing us to more rapidly design and build out the large, complicated and interoperable enterprise SOAs into which our IT environments are evolving.”

- Al Gough, Business Systems Solutions CTO, CACI International Inc.

 

“This book provides a comprehensive and pragmatic review of design issues in service-centric design, development, and evolution. The Web site related to this book [SOAPatterns.org] is a wonderful platform and gives the opportunity for the software community to maintain this catalogue….”

- Veronica Gacitua Decar, Dublin City University

 

“Erl’s SOA Design Patterns is for the IT decision maker determined to make smart architecture design choices, smart investments, and long term enterprise impact. For those IT professionals committed to service-orientation as a value-added design and implementation option, Patterns offers a credible, repeatable approach to engineering an adaptable business enterprise. This is a must read for all IT architect professionals.”

- Larry Gloss, VP and General Manager, Information Manufacturing, LLC

 

“These SOA patterns define, encompass, and comprise a complete repertoire of best practices for developing a world-class IT SOA portfolio for the enterprise and its organizational units through to service and schema analysis and design. After many years as an architect on many SOA projects, I strongly recommend this book be on the shelf of every analyst and technical member of any SOA effort, right next to the SOA standards and guidelines it outlines and elucidates the need for. Our SOA governance standards draw heavily from this work and others from this series.”

- Robert John Hathaway III, Enterprise Software Architect, SOA Object Systems

 

“A wise man once told me that wisdom isn’t all about knowledge and intelligence, it is just as much about asking questions. Asking questions is the true mark of wisdom and during the writing of the SOA Design Patterns book Thomas Erl has shown his real qualities. The community effort behind this book is huge meaning that Thomas has had access to the knowledge and experience of a large group of accomplished practitioners. The result speaks for itself. This book is packed with proven solutions to recurring problems, and the documented pros and cons of each solution have been verified by persons with true experience. This book could give SOA initiatives of any scale a real boost.”

- Herbjörn Wilhelmsen, Architect and Senior Consultant, Objectware

 

“This book is an absolute milestone in SOA literature. For the first time we are provided with a practical guide on how the principle centric description of service orientation from a vendor-agnostic viewpoint is actually made to work in a language based on patterns. This book makes you talk SOA! There are very few who understand SOA like Thomas Erl does, he actually put’s it all together!”

- Brian Lokhorst, Solution Architect, Dutch Tax Office

 

“Service oriented architecture is all about best practices we have learned since IT’s existence. This book takes all those best practices and bundles them into a nice pattern catalogue. [It provides] a really excellent approach as patterns are not just documented but are provided with application scenarios through case studies [which] fills the gap between theory and practice.”

- Shakti Sharma, Senior Enterprise Architect, Sysco Corp

 

“An excellent and important book on solving problems in SOA [with a] solid structure. Has the potential of being among the major influential books.”

- Peter Chang, Lawrence Technical University

 

“SOA Design Patterns presents a vast amount of knowledge about how to successfully implement SOA within an organization. The information is clear, concise, and most importantly, legitimate.”

- Peter B. Woodhull, President and Principal Architect, Modus21

 

“SOA Design Patterns offers real insights into everyday problems that one will encounter when investing in services oriented architecture. [It] provides a number of problem descriptions and offers strategies for dealing with these problems. SOA design patterns highlights more than just the technical problems and solutions. Common organizational issues that can hinder progress towards achieving SOA migration are explained along with potential approaches for dealing with these real world challenges. Once again Thomas Erl provides in-depth coverage of SOA terminology and helps the reader better understand and appreciate the complexities of migrating to an SOA environment.”

- David Michalowicz, Air and Space Operations Center Modernization Team Lead,

MITRE Corporation

 

“This is a long overdue, serious, comprehensive, and well-presented catalog of SOA design patterns. This will be required reading and reference for all our SOA engineers and architects. The best of the series so far!

 

[The book] works in two ways: as a primer in SOA design and architecture it can easily be read front-to-back to get an overview of most of the key design issues you will encounter, and as a reference catalog of design techniques that can be referred to again and again…”

- Wendell Ocasio, Architecture Consultant, DoD Military Health Systems, Agilex Technologies

 

“Thomas has once again provided the SOA practitioner with a phenomenal collection of

knowledge. This is a reference that I will come back to time and time again as I move forward in SOA design efforts.

 

What I liked most about this book is its vendor agnostic approach to SOA design patterns. This approach really presents the reader with an understanding of why or why not to implement a pattern, group patterns, or use compound patterns rather than giving them a marketing spiel on why one implementation of a pattern is better than another (for example, why one ESB is better than another). I think as SOA adoption continues to advance, the ability for architects to understand when and why to apply specific patterns will be a driving factor in the overall success and evolution of SOA. Additionally, I believe that this book provides the consumer with the understanding required to chose which vendor’s SOA products are right for their specific needs.”

- Bryan Brew, SOA Consultant, Booz Allen Hamilton

 

“A must have for every SOA practitioner.”

- Richard Van Schelven, Principal Engineer, Ericsson

 

“This book is a long-expected successor to the books on object-oriented design patterns and integration patterns. It is a great reference book that clearly and thoroughly describes design patterns for SOA. A great read for architects who are facing the challenge of transforming their enterprise into a service-oriented enterprise.”

- Linda Terlouw, Solution Architect, Ordina

 

“The maturation of Service-Orientation has given the industry time to absorb the best practices of service development. Thomas Erl has amassed this collective wisdom in SOA Design Patterns, an absolutely indispensible addition to any Service Oriented bookshelf.”

- Kevin P. Davis, Ph.D

 

“The problem with most texts on SOA is one of specificity. Architects responsible for SOA implementation in most organizations have little time for abstract theories on the subject, but are hungry for concrete details that they can relate to the real problems they face in their environment. SOA Design Patterns is critical reading for anyone with service design responsibilities. Not only does the text provide the normal pattern templates, but each pattern is applied in detail against a background case study to provide exceptionally meaningful context to the information. The graphic visualizations of the problems and pattern solutions are excellent supplementary companions to the explanatory text. This book will greatly stretch the knowledge of the reader as much for raising and addressing issues that may have never occurred to the reader as it does in treating those problems that are in more common occurrence. The real beauty of this book is in its plain English prose. Unlike so many technical reference books, one does not find themselves re-reading sections multiple times trying to discern the intent of the author. This is also not a reference that will sit gathering dust on a shelf after one or two perusings. Practitioners will find themselves returning over and over to utilize the knowledge in their projects. This is as close as you’ll come to having a service design expert sitting over your shoulder.”

- James Kinneavy, Principal Software Architect, University of California

 

“As the industry converges on SOA patterns, Erl provides an outstanding reference guide to composition and integration–and yet another distinctive contribution to the SOA practice.”

- Steve Birkel, Chief IT Technical Architect, Intel Corp.

 

“With SOA Design Patterns, Thomas Erl adds an indispensable SOA reference volume to the technologist’s library. Replete with to-the-point examples, it will be a helpful aid to any IT organization.”

- Ed Dodds, Strategist, Systems Architect, Conmergence

 

“Again, Thomas Erl has written an indispensable guide to SOA. Building on his prior successes, his patterns go into even more detail. Therefore, this book is not only helpful to the SOA beginner, but also provides new insight and ideas to professionals.”

- Philipp Offermann, Research Scientist, Technische Universität Berlin, Germany

 

“SOA Design Patterns is an extraordinary contribution to SOA best practices! Once again, Thomas has created an indispensable resource for any person or organization interested in or actively engaged in the practice of Service Oriented Architecture. Using case studies based on three very different business models, Thomas guides the reader through the process of selecting appropriate implementation patterns to ensure a flexible, well-performing, and secure SOA ecosystem.”

- Victor Brown, Managing Partner and Principal Consultant,

Cypress Management Group Corporation

 In cooperation with experts and practitioners throughout the SOA community, best-selling author Thomas Erl brings together the de facto catalog of design patterns for SOA and service-orientation. More than three years in development and subjected to numerous industry reviews, the 85 patterns in this full-color book provide the most successful and proven design techniques to overcoming the most common and critical problems to achieving modern-day SOA. Through numerous examples, individually documented pattern profiles, and over 400 color illustrations, this book provides in-depth coverage of: •  Patterns for the design, implementation, and governance of service inventories–collections of services representing individual service portfolios that can be independently modeled, designed, and evolved. •   Patterns specific to service-level architecture which pertain to a wide range of design areas, including contract design, security, legacy encapsulation, reliability, scalability, and a variety of implementation and governance issues. •   Service composition patterns that address the many aspects associated with combining services into aggregate distributed solutions, including topics such as runtime messaging and message design, inter-service security controls, and transformation. •   Compound patterns (such as Enterprise Service Bus and Orchestration) and recommended pattern application sequences that establish foundational processes. The book begins by establishing SOA types that are referenced throughout the patterns and then form the basis of a final chapter that discusses the architectural impact of service-oriented computing in general. These chapters bookend the pattern catalog to provide a clear link between SOA design patterns, the strategic goals of service-oriented computing, different SOA types, and the service-orientation design paradigm.

 

This book series is further supported by a series of resources sites, including
soabooks.com, soaspecs.com, soapatterns.org, soamag.com, and soaposters.com.

Specificaties

ISBN13:9780138158194
Taal:Engels
Bindwijze:e-book

Lezersrecensies

Wees de eerste die een lezersrecensie schrijft!

Inhoudsopgave

<div sercontent=""> <p style="MARGIN: 0px">Foreword...xxxvii</p> <p style="MARGIN: 0px">CHAPTER 1: Introduction...1</p> <p style="MARGIN: 0px">1.1 Objectives of this Book&nbsp;... 4</p> <p style="MARGIN: 0px">1.2 Who this Book is For&nbsp;... 4</p> <p style="MARGIN: 0px">1.3 What this Book Does Not Cover...&nbsp; 4</p> <p style="MARGIN: 0px">Topics Covered by Other Books&nbsp; ...4</p> <p style="MARGIN: 0px">Web Service and REST Service Design Patterns&nbsp;... 5</p> <p style="MARGIN: 0px">SOA Standardization Efforts...&nbsp; 5</p> <p style="MARGIN: 0px">1.4 Recommended Reading&nbsp;... 6</p> <p style="MARGIN: 0px">1.5 How this Book is Organized...&nbsp; 7</p> <p style="MARGIN: 0px">Part I: Fundamentals...&nbsp; 8</p> <p style="MARGIN: 0px">Part II: Service Inventory Design Patterns...&nbsp; 8</p> <p style="MARGIN: 0px">Part III: Service Design Patterns&nbsp; . . 8</p> <p style="MARGIN: 0px">Part IV: Service Composition Design Patterns&nbsp; . . 9</p> <p style="MARGIN: 0px">Part V: Supplemental. . . 10</p> <p style="MARGIN: 0px">Part VI: Appendices . . . 10</p> <p style="MARGIN: 0px">1.6 Symbols, Figures, Style Conventions&nbsp; . . . 11</p> <p style="MARGIN: 0px">Symbol Legend&nbsp; . . . 11</p> <p style="MARGIN: 0px">How Color is Used&nbsp; 11</p> <p style="MARGIN: 0px">Data Flow and Directionality Conventions&nbsp; . . 11</p> <p style="MARGIN: 0px">Pattern Documentation Conventions&nbsp; . 11</p> <p style="MARGIN: 0px">1.7 Additional Information&nbsp;&nbsp;&nbsp; 11</p> <p style="MARGIN: 0px">Updates, Errata, and Resources (www.soabooks.com)&nbsp; . . . . 11</p> <p style="MARGIN: 0px">Visio Stencil (www.soabooks.com)&nbsp;&nbsp; . 12</p> <p style="MARGIN: 0px">Community Patterns Site (www.soapatterns.org)&nbsp; .&nbsp; . . . . 12</p> <p style="MARGIN: 0px">Master Glossary (www.soaglossary.com)&nbsp; 12</p> <p style="MARGIN: 0px">Supplementary Posters (www.soaposters.com)&nbsp; 12</p> <p style="MARGIN: 0px">The SOA Magazine (www.soamag.com)&nbsp; 12</p> <p style="MARGIN: 0px">Referenced Specifications (www.soaspecs.com).&nbsp; .&nbsp; . . . 12</p> <p style="MARGIN: 0px">Notification Service&nbsp; 13</p> <p style="MARGIN: 0px">Contact the Author&nbsp; 13</p> <p style="MARGIN: 0px">CHAPTER 2: Case Study Background&nbsp; . 15</p> <p style="MARGIN: 0px">2.1 Case #1 Background: Cutit Saws Ltd&nbsp; 17</p> <p style="MARGIN: 0px">History&nbsp; 18</p> <p style="MARGIN: 0px">Technical Infrastructure and Automation Environment&nbsp; .&nbsp; 18</p> <p style="MARGIN: 0px">Business Goals and Obstacles.&nbsp; . 18</p> <p style="MARGIN: 0px">2.2 Case #2 Background: Alleywood Lumber Company&nbsp; . 19</p> <p style="MARGIN: 0px">History&nbsp; 19</p> <p style="MARGIN: 0px">Technical Infrastructure and Automation Environment&nbsp; .&nbsp; 20</p> <p style="MARGIN: 0px">Business Goals and Obstacles.&nbsp; . 20</p> <p style="MARGIN: 0px">2.3 Case #3 Background: Forestry Regulatory</p> <p style="MARGIN: 0px">Commission (FRC) . . 21</p> <p style="MARGIN: 0px">History&nbsp; 21</p> <p style="MARGIN: 0px">Technical Infrastructure and Automation Environment&nbsp; .&nbsp; 21</p> <p style="MARGIN: 0px">Business Goals and Obstacles.&nbsp; . 22</p> <p style="MARGIN: 0px">PART I: FUNDAMENTALS</p> <p style="MARGIN: 0px">CHAPTER 3: Basic Terms and Concepts&nbsp; .&nbsp; . . . . 25</p> <p style="MARGIN: 0px">Purpose of this Introductory Chapter&nbsp; . . . 26</p> <p style="MARGIN: 0px">3.1 Architecture Fundamentals&nbsp; 26</p> <p style="MARGIN: 0px">A Classic Analogy for Architecture and Infrastructure&nbsp; .&nbsp; 27</p> <p style="MARGIN: 0px">Technology Architecture 27</p> <p style="MARGIN: 0px">Technology Infrastructure&nbsp; . 30</p> <p style="MARGIN: 0px">Software Program&nbsp; . 32</p> <p style="MARGIN: 0px">Relationship to Design Framework&nbsp;&nbsp; . 33</p> <p style="MARGIN: 0px">3.2 Service-Oriented Computing Fundamentals.&nbsp; .&nbsp; . . 35</p> <p style="MARGIN: 0px">Service-Oriented Computing&nbsp; . . . 35</p> <p style="MARGIN: 0px">Service-Orientation&nbsp; 36</p> <p style="MARGIN: 0px">Service-Oriented Architecture (SOA)&nbsp; . . . 37</p> <p style="MARGIN: 0px">Service&nbsp; .&nbsp; . . . . 37</p> <p style="MARGIN: 0px">Service Capability&nbsp; . 38</p> <p style="MARGIN: 0px">Service Consumer.&nbsp; 38</p> <p style="MARGIN: 0px">Service Composition . . . 40</p> <p style="MARGIN: 0px">Service Inventory.&nbsp; . 42</p> <p style="MARGIN: 0px">Service-Oriented Analysis.&nbsp; 43</p> <p style="MARGIN: 0px">Service Candidate.&nbsp; 44</p> <p style="MARGIN: 0px">3.3 Service Implementation Mediums&nbsp; . . . 44</p> <p style="MARGIN: 0px">Services as Components&nbsp; . 45</p> <p style="MARGIN: 0px">Services as Web Services&nbsp; 45</p> <p style="MARGIN: 0px">REST Services.&nbsp; . . . 46</p> <p style="MARGIN: 0px">CHAPTER 4: The Architecture of Service-Orientation . . 47</p> <p style="MARGIN: 0px">Purpose of this Introductory Chapter&nbsp; . . . 48</p> <p style="MARGIN: 0px">4.1 The Method of Service-Orientation&nbsp; 48</p> <p style="MARGIN: 0px">Principles of Service-Orientation.&nbsp; 48</p> <p style="MARGIN: 0px">Strategic Goals of Service-Oriented Computing.&nbsp; .&nbsp; . . . . 51</p> <p style="MARGIN: 0px">4.2 The Four Characteristics of SOA&nbsp;&nbsp; 52</p> <p style="MARGIN: 0px">Business-Driven&nbsp; . . 53</p> <p style="MARGIN: 0px">Vendor-Neutral&nbsp; . . . 54</p> <p style="MARGIN: 0px">Enterprise-Centric&nbsp; . 58</p> <p style="MARGIN: 0px">Composition-Centric . . . 59</p> <p style="MARGIN: 0px">4.3 The Four Common Types of SOA&nbsp; . 61</p> <p style="MARGIN: 0px">Service Architecture . . . 62</p> <p style="MARGIN: 0px">Information Hiding&nbsp; . . . . 64</p> <p style="MARGIN: 0px">Design Standards&nbsp; .&nbsp; 64</p> <p style="MARGIN: 0px">Service Contracts&nbsp; .&nbsp; 65</p> <p style="MARGIN: 0px">Service Agents&nbsp; .&nbsp; . . 67</p> <p style="MARGIN: 0px">Service Capabilities&nbsp; . . . 68</p> <p style="MARGIN: 0px">Service Composition Architecture&nbsp;&nbsp; . 68</p> <p style="MARGIN: 0px">Nested Compositions&nbsp; . . 72</p> <p style="MARGIN: 0px">Task Services and Alternative Compositions&nbsp; . 73</p> <p style="MARGIN: 0px">Compositions and Infrastructure.&nbsp;&nbsp;&nbsp; 74</p> <p style="MARGIN: 0px">Service Inventory Architecture&nbsp; . . 74</p> <p style="MARGIN: 0px">Service-Oriented Enterprise Architecture&nbsp;&nbsp; 76</p> <p style="MARGIN: 0px">Architecture Types and Scope&nbsp; . . 77</p> <p style="MARGIN: 0px">Architecture Types and Inheritance&nbsp;&nbsp; 77</p> <p style="MARGIN: 0px">Other Forms of Service-Oriented Architecture&nbsp; . 78</p> <p style="MARGIN: 0px">Inter-Business Service Architecture&nbsp; . . 78</p> <p style="MARGIN: 0px">Service-Oriented Community Architecture&nbsp; . . 78</p> <p style="MARGIN: 0px">4.4 The End Result of Service-Orientation&nbsp; . . 79</p> <p style="MARGIN: 0px">CHAPTER 5: Understanding SOA Design Patterns&nbsp; . 85</p> <p style="MARGIN: 0px">Purpose of this Introductory Chapter&nbsp; . . . 86</p> <p style="MARGIN: 0px">5.1 Fundamental Terminology.&nbsp; 86</p> <p style="MARGIN: 0px">What’s a Design Pattern?&nbsp; . 86</p> <p style="MARGIN: 0px">What’s a Compound Pattern?&nbsp; . . . 88</p> <p style="MARGIN: 0px">What’s a Design Pattern Language?&nbsp; . 88</p> <p style="MARGIN: 0px">What’s a Design Pattern Catalog?&nbsp; . . . 89</p> <p style="MARGIN: 0px">5.2 Historical Influences&nbsp; 89</p> <p style="MARGIN: 0px">Alexander’s Pattern Language&nbsp; . . 90</p> <p style="MARGIN: 0px">Object-Oriented Patterns&nbsp; . 91</p> <p style="MARGIN: 0px">Software Architecture Patterns&nbsp; . . 92</p> <p style="MARGIN: 0px">Enterprise Application Architecture Patterns&nbsp; . . 93</p> <p style="MARGIN: 0px">EAI Patterns&nbsp; .&nbsp; 93</p> <p style="MARGIN: 0px">SOA Patterns&nbsp; . . . . 94</p> <p style="MARGIN: 0px">5.3 Pattern Notation . 95</p> <p style="MARGIN: 0px">Pattern Symbols&nbsp; . . 95</p> <p style="MARGIN: 0px">Pattern Figures&nbsp; . . . 96</p> <p style="MARGIN: 0px">Pattern Application Sequence Figures&nbsp; 96</p> <p style="MARGIN: 0px">Pattern Relationship Figures. 96</p> <p style="MARGIN: 0px">Compound Pattern Hierarchy Figures&nbsp; 99</p> <p style="MARGIN: 0px">Capitalization.&nbsp; . . . 100</p> <p style="MARGIN: 0px">Page Number References.&nbsp;&nbsp;&nbsp; 100</p> <p style="MARGIN: 0px">5.4 Pattern Profiles . 100</p> <p style="MARGIN: 0px">Requirement&nbsp; . . . . 101</p> <p style="MARGIN: 0px">Icon&nbsp; . 101</p> <p style="MARGIN: 0px">Summary&nbsp; .&nbsp; . 102</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 102</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 102</p> <p style="MARGIN: 0px">Application&nbsp; .&nbsp; 103</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 103</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 103</p> <p style="MARGIN: 0px">Case Study Example. . 103</p> <p style="MARGIN: 0px">5.5 Patterns with Common Characteristics.&nbsp; 104</p> <p style="MARGIN: 0px">Canonical Patterns . . . 104</p> <p style="MARGIN: 0px">Centralization Patterns 105</p> <p style="MARGIN: 0px">5.6 Key Design Considerations&nbsp; . . 106</p> <p style="MARGIN: 0px">“Enterprise” vs. “Enterprise-wide”&nbsp; . . 106</p> <p style="MARGIN: 0px">Design Patterns and Design Principles&nbsp; 106</p> <p style="MARGIN: 0px">Design Patterns and Design Granularity&nbsp; . . 107</p> <p style="MARGIN: 0px">Measures of Design Pattern Application&nbsp; . . 108</p> <p style="MARGIN: 0px">PART II: SERVICE INVENTORY DESIGN PATTERNS</p> <p style="MARGIN: 0px">CHAPTER 6: Foundational Inventory Patterns&nbsp; . . . 111</p> <p style="MARGIN: 0px">How Inventory Design Patterns Relate to SOA Design</p> <p style="MARGIN: 0px">Characteristics&nbsp; . . 113</p> <p style="MARGIN: 0px">How Foundational Inventory and Service Patterns Relate&nbsp; . 114</p> <p style="MARGIN: 0px">How Case Studies are Used in this Chapter.&nbsp; . 114</p> <p style="MARGIN: 0px">6.1 Inventory Boundary Patterns&nbsp; . 114</p> <p style="MARGIN: 0px">Enterprise Inventory&nbsp; . 116</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 116</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 117</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 118</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 120</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 121</p> <p style="MARGIN: 0px">Case Study Example. . 122</p> <p style="MARGIN: 0px">Domain Inventory . 123</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 123</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 124</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 125</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 126</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 127</p> <p style="MARGIN: 0px">Case Study Example. . 128</p> <p style="MARGIN: 0px">6.2 Inventory Structure Patterns&nbsp;&nbsp; 130</p> <p style="MARGIN: 0px">Service Normalization.&nbsp;&nbsp;&nbsp; 131</p> <p style="MARGIN: 0px">Problem &nbsp;.&nbsp; . . . 131</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 132</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 132</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 133</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 133</p> <p style="MARGIN: 0px">Case Study Example. . 135</p> <p style="MARGIN: 0px">Logic Centralization&nbsp; . 136</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 136</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 137</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 137</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 139</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 140</p> <p style="MARGIN: 0px">Case Study Example. . 142</p> <p style="MARGIN: 0px">Service Layers&nbsp; 143</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 143</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 144</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 145</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 147</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 147</p> <p style="MARGIN: 0px">Case Study Example. . 148</p> <p style="MARGIN: 0px">6.3 Inventory Standardization Patterns&nbsp;&nbsp; 149</p> <p style="MARGIN: 0px">Canonical Protocol 150</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 151</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 152</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 153</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 155</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 155</p> <p style="MARGIN: 0px">Case Study Example. . 157</p> <p style="MARGIN: 0px">Canonical Schema 158</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 158</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 159</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 159</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 159</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 160</p> <p style="MARGIN: 0px">Case Study Example. . 161</p> <p style="MARGIN: 0px">CHAPTER 7: Logical Inventory Layer Patterns&nbsp; . . . 163</p> <p style="MARGIN: 0px">Combining Layers&nbsp; 164</p> <p style="MARGIN: 0px">Business Logic and Utility Logic&nbsp; . . . 166</p> <p style="MARGIN: 0px">Agnostic Logic and Non-Agnostic Logic&nbsp;&nbsp; 166</p> <p style="MARGIN: 0px">Service Layers and Logic Types&nbsp; . . . 167</p> <p style="MARGIN: 0px">Utility Abstraction . 168</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 168</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 169</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 170</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 171</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 171</p> <p style="MARGIN: 0px">Case Study Example. . 173</p> <p style="MARGIN: 0px">Entity Abstraction . 175</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 175</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 176</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 176</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 178</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 178</p> <p style="MARGIN: 0px">Case Study Example. . 180</p> <p style="MARGIN: 0px">Process Abstraction&nbsp; . 182</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 182</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 183</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 184</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 185</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 185</p> <p style="MARGIN: 0px">Case Study Example. . 187</p> <p style="MARGIN: 0px">CHAPTER 8: Inventory Centralization Patterns&nbsp; . . 191</p> <p style="MARGIN: 0px">Process Centralization&nbsp;&nbsp;&nbsp; 193</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 193</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 194</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 195</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 196</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 197</p> <p style="MARGIN: 0px">Case Study Example. . 198</p> <p style="MARGIN: 0px">Schema Centralization&nbsp;&nbsp;&nbsp; 200</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 200</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 201</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 202</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 202</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 203</p> <p style="MARGIN: 0px">Case Study Example. . 203</p> <p style="MARGIN: 0px">Policy Centralization&nbsp; . 207</p> <p style="MARGIN: 0px">Problems&nbsp; .&nbsp; . . 207</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 208</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 209</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 210</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 211</p> <p style="MARGIN: 0px">Case Study Example. . 213</p> <p style="MARGIN: 0px">Rules Centralization&nbsp; . 216</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 216</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 217</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 217</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 218</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 219</p> <p style="MARGIN: 0px">Case Study Example. . 222</p> <p style="MARGIN: 0px">CHAPTER 9: Inventory Implementation Patterns&nbsp; . 225</p> <p style="MARGIN: 0px">Dual Protocols&nbsp; 227</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 228</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 228</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 228</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 233</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 234</p> <p style="MARGIN: 0px">Case Study Example. . 235</p> <p style="MARGIN: 0px">Canonical Resources&nbsp; 237</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 238</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 238</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 239</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 239</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 239</p> <p style="MARGIN: 0px">Case Study Example. . 241</p> <p style="MARGIN: 0px">State Repository . . 242</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 242</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 243</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 244</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 244</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 244</p> <p style="MARGIN: 0px">Case Study Example. . 246</p> <p style="MARGIN: 0px">Stateful Services . . 248</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 248</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 248</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 250</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 250</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 250</p> <p style="MARGIN: 0px">Case Study Example. . 251</p> <p style="MARGIN: 0px">Service Grid&nbsp; . . 254</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 254</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 255</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 256</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 257</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 258</p> <p style="MARGIN: 0px">Case Study Example. . 259</p> <p style="MARGIN: 0px">Inventory Endpoint 260</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 260</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 261</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 262</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 263</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 263</p> <p style="MARGIN: 0px">Case Study Example. . 265</p> <p style="MARGIN: 0px">Cross-Domain Utility Layer&nbsp; 267</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 267</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 268</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 269</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 269</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 270</p> <p style="MARGIN: 0px">Case Study Example. . 270</p> <p style="MARGIN: 0px">CHAPTER 10: Inventory Governance Patterns&nbsp; . . . 273</p> <p style="MARGIN: 0px">Canonical Expression.&nbsp;&nbsp;&nbsp; 275</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 275</p> <p style="MARGIN: 0px">Solution&nbsp; . &nbsp;. . . 275</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 276</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 277</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 278</p> <p style="MARGIN: 0px">Case Study Example. . 279</p> <p style="MARGIN: 0px">Metadata Centralization&nbsp; . . . 280</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 280</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 281</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 282</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 283</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 283</p> <p style="MARGIN: 0px">Case Study Example. . 284</p> <p style="MARGIN: 0px">Canonical Versioning&nbsp; 286</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 286</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 287</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 287</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 288</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 288</p> <p style="MARGIN: 0px">Case Study Example. . 290</p> <p style="MARGIN: 0px">PART III: SERVICE DESIGN PATTERNS</p> <p style="MARGIN: 0px">CHAPTER 11: Foundational Service Patterns&nbsp; . . . . 295</p> <p style="MARGIN: 0px">Case Study Background&nbsp;&nbsp;&nbsp; 297</p> <p style="MARGIN: 0px">11.1 Service Identification Patterns&nbsp; . 299</p> <p style="MARGIN: 0px">Functional Decomposition&nbsp; . 300</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 300</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 301</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 302</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 302</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 303</p> <p style="MARGIN: 0px">Case Study Example. . 303</p> <p style="MARGIN: 0px">Service Encapsulation&nbsp;&nbsp;&nbsp; 305</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 305</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 306</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 307</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 309</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 309</p> <p style="MARGIN: 0px">Case Study Example. . 310</p> <p style="MARGIN: 0px">11.2 Service Definition Patterns&nbsp;&nbsp; 311</p> <p style="MARGIN: 0px">Agnostic Context. . 312</p> <p style="MARGIN: 0px">Problem&nbsp; . &nbsp;. . . 313</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 314</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 315</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 315</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 316</p> <p style="MARGIN: 0px">Case Study Example. . 317</p> <p style="MARGIN: 0px">Non-Agnostic Context&nbsp;&nbsp;&nbsp; 319</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 319</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 320</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 321</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 322</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 322</p> <p style="MARGIN: 0px">Case Study Example. . 323</p> <p style="MARGIN: 0px">Agnostic Capability324</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 324</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 325</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 326</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 327</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 327</p> <p style="MARGIN: 0px">Case Study Example. . 328</p> <p style="MARGIN: 0px">CHAPTER 12: Service Implementation Patterns.&nbsp; . 331</p> <p style="MARGIN: 0px">Service Façade . . . 333</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 333</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 334</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 335</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 341</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 342</p> <p style="MARGIN: 0px">Case Study Example. . 343</p> <p style="MARGIN: 0px">Redundant Implementation&nbsp; 345</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 345</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 346</p> <p style="MARGIN: 0px">Application.&nbsp; . &nbsp;346</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 347</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 348</p> <p style="MARGIN: 0px">Case Study Example. . 349</p> <p style="MARGIN: 0px">Service Data Replication&nbsp; . . 350</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 350</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 352</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 353</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 353</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 353</p> <p style="MARGIN: 0px">Case Study Example. . 354</p> <p style="MARGIN: 0px">Partial State Deferral&nbsp; . 356</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 356</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 357</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 358</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 359</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 359</p> <p style="MARGIN: 0px">Case Study Example. . 360</p> <p style="MARGIN: 0px">Partial Validation . . 362</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 362</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 363</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 364</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 364</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 364</p> <p style="MARGIN: 0px">Case Study Example. . 365</p> <p style="MARGIN: 0px">UI Mediator.&nbsp; . . 366</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 366</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 367</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 368</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 369</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 370</p> <p style="MARGIN: 0px">Case Study Example. . 370</p> <p style="MARGIN: 0px">CHAPTER 13: Service Security Patterns&nbsp; .&nbsp; . . 373</p> <p style="MARGIN: 0px">Case Study background&nbsp;&nbsp;&nbsp; 374</p> <p style="MARGIN: 0px">Exception Shielding&nbsp; . 376</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 376</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 377</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 378</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 379</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 379</p> <p style="MARGIN: 0px">Case Study Example. . 380</p> <p style="MARGIN: 0px">Message Screening381</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 381</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 382</p> <p style="MARGIN: 0px">Application&nbsp; .&nbsp; 382</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 384</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 385</p> <p style="MARGIN: 0px">Case Study Example. . 385</p> <p style="MARGIN: 0px">Trusted Subsystem 387</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 387</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 388</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 388</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 391</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 391</p> <p style="MARGIN: 0px">Case Study Example. . 392</p> <p style="MARGIN: 0px">Service Perimeter Guard&nbsp; 394</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 394</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 395</p> <p style="MARGIN: 0px">Application&nbsp; .&nbsp; 395</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 396</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 396</p> <p style="MARGIN: 0px">Case Study Example. . 397</p> <p style="MARGIN: 0px">CHAPTER 14: Service Contract Design Patterns&nbsp; . 399</p> <p style="MARGIN: 0px">Decoupled Contract&nbsp; . 401</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 401</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 402</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 403</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 405</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 405</p> <p style="MARGIN: 0px">Case Study Example. . 407</p> <p style="MARGIN: 0px">Contract Centralization&nbsp; . 409</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 409</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 410</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 410</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 411</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 411</p> <p style="MARGIN: 0px">Case Study Example. . 413</p> <p style="MARGIN: 0px">Contract Denormalization.&nbsp; . 414</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 414</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 415</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 416</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 417</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 417</p> <p style="MARGIN: 0px">Case Study Example. . 418</p> <p style="MARGIN: 0px">Concurrent Contracts&nbsp; 421</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 421</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 422</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 423</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 425</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 425</p> <p style="MARGIN: 0px">Case Study Example. . 426</p> <p style="MARGIN: 0px">Validation Abstraction&nbsp;&nbsp;&nbsp; 429</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 429</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 430</p> <p style="MARGIN: 0px">Application. &nbsp;.&nbsp; 431</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 432</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 432</p> <p style="MARGIN: 0px">Case Study Example. . 433</p> <p style="MARGIN: 0px">Chapter 15: Legacy Encapsulation Patterns&nbsp; . . . 439</p> <p style="MARGIN: 0px">Legacy Wrapper. . . 441</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 441</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 442</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 443</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 444</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 444</p> <p style="MARGIN: 0px">Case Study Example. . 446</p> <p style="MARGIN: 0px">Multi-Channel Endpoint&nbsp; . . . 451</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 451</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 452</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 453</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 454</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 454</p> <p style="MARGIN: 0px">Case Study Example. . 456</p> <p style="MARGIN: 0px">File Gateway&nbsp; . 457</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 457</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 458</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 458</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 459</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 460</p> <p style="MARGIN: 0px">Case Study Example. . 461</p> <p style="MARGIN: 0px">CHAPTER 16: Service Governance Patterns.&nbsp; . . . . 463</p> <p style="MARGIN: 0px">Compatible Change465</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 465</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 466</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 466</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 469</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 469</p> <p style="MARGIN: 0px">Case Study Example. . 470</p> <p style="MARGIN: 0px">Version Identification&nbsp; 472</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 472</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 473</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 473</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 474</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 474</p> <p style="MARGIN: 0px">Case Study Example. . 475</p> <p style="MARGIN: 0px">Termination Notification&nbsp; . . . 478</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 478</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 479</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 480</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 480</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 481</p> <p style="MARGIN: 0px">Case Study Example. . 481</p> <p style="MARGIN: 0px">Service Refactoring484</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 484</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 485</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 485</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 486</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 486</p> <p style="MARGIN: 0px">Case Study Example. . 488</p> <p style="MARGIN: 0px">Service Decomposition&nbsp; . 489</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 489</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 491</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 492</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 492</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 494</p> <p style="MARGIN: 0px">Case Study Example. . 495</p> <p style="MARGIN: 0px">Proxy Capability . . 497</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 497</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 498</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 498</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 500</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 500</p> <p style="MARGIN: 0px">Case Study Example. . 501</p> <p style="MARGIN: 0px">Decomposed Capability&nbsp; . . . 504</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 504</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 506</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 507</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 507</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 508</p> <p style="MARGIN: 0px">Case Study Example. . 508</p> <p style="MARGIN: 0px">Distributed Capability&nbsp; 510</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 510</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 511</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 512</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 513</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 513</p> <p style="MARGIN: 0px">Case Study Example. . 514</p> <p style="MARGIN: 0px">PART IV: SERVICE COMPOSITION DESIGN PATTERNS</p> <p style="MARGIN: 0px">CHAPTER 17: Capability Composition Patterns&nbsp; . . 519</p> <p style="MARGIN: 0px">Capability Composition&nbsp; . . . 521</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 521</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 521</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 523</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 523</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 523</p> <p style="MARGIN: 0px">Case Study Example. . 524</p> <p style="MARGIN: 0px">Capability Recomposition&nbsp; . 526</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 526</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 527</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 527</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 527</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 529</p> <p style="MARGIN: 0px">Case Study Example. . 530</p> <p style="MARGIN: 0px">CHAPTER 18: Service Messaging Patterns.&nbsp; .&nbsp; 531</p> <p style="MARGIN: 0px">Service Messaging 533</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 533</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 533</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 534</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 534</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 535</p> <p style="MARGIN: 0px">Case Study Example. . 536</p> <p style="MARGIN: 0px">Messaging Metadata&nbsp; 538</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 538</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 538</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 539</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 540</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 541</p> <p style="MARGIN: 0px">Case Study Example. . 542</p> <p style="MARGIN: 0px">Service Agent&nbsp; 543</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 543</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 544</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 544</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 546</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 546</p> <p style="MARGIN: 0px">Case Study Example. . 548</p> <p style="MARGIN: 0px">Intermediate Routing&nbsp; 549</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 549</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 551</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 552</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 553</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 553</p> <p style="MARGIN: 0px">Case Study Example. . 556</p> <p style="MARGIN: 0px">State Messaging . . 557</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 557</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 558</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 560</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 561</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 561</p> <p style="MARGIN: 0px">Case Study Example. . 562</p> <p style="MARGIN: 0px">Service Callback . . 566</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 566</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 568</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 568</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 570</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 570</p> <p style="MARGIN: 0px">Case Study Example. . 571</p> <p style="MARGIN: 0px">Service Instance Routing&nbsp; . . 574</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 574</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 576</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 576</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 578</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 578</p> <p style="MARGIN: 0px">Case Study Example. . 579</p> <p style="MARGIN: 0px">Asynchronous Queuing&nbsp; . . . 582</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 582</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 584</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 584</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 587</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 588</p> <p style="MARGIN: 0px">Case Study Example. . 589</p> <p style="MARGIN: 0px">Reliable Messaging 592</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 592</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 593</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 593</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 594</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 595</p> <p style="MARGIN: 0px">Case Study Example. . 596</p> <p style="MARGIN: 0px">Event-Driven Messaging&nbsp; 599</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 599</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 600</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 602</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 602</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 602</p> <p style="MARGIN: 0px">Case Study Example. . 604</p> <p style="MARGIN: 0px">CHAPTER 19: Composition Implementation Patterns . . 605</p> <p style="MARGIN: 0px">Agnostic Sub-Controller&nbsp; 607</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 607</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 608</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 610</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 610</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 610</p> <p style="MARGIN: 0px">Case Study Example. . 612</p> <p style="MARGIN: 0px">Composition Autonomy&nbsp; . . . 616</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 616</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 618</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 619</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 619</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 620</p> <p style="MARGIN: 0px">Case Study Example. . 620</p> <p style="MARGIN: 0px">Atomic Service Transaction&nbsp; 623</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 623</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 624</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 626</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 626</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 628</p> <p style="MARGIN: 0px">Case Study Example. . 629</p> <p style="MARGIN: 0px">Compensating Service Transaction&nbsp; . . 631</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 631</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 633</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 633</p> <p style="MARGIN: 0px">Impacts &nbsp;.&nbsp; . . . 635</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 635</p> <p style="MARGIN: 0px">Case Study Example. . 636</p> <p style="MARGIN: 0px">CHAPTER 20: Service Interaction Security Patterns . . 639</p> <p style="MARGIN: 0px">Data Confidentiality641</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 641</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 643</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 643</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 644</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 645</p> <p style="MARGIN: 0px">Case Study Example. . 646</p> <p style="MARGIN: 0px">Data Origin Authentication.&nbsp; 649</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 649</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 650</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 651</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 652</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 653</p> <p style="MARGIN: 0px">Case Study Example. . 653</p> <p style="MARGIN: 0px">Direct Authentication&nbsp; 656</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 656</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 657</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 657</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 658</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 659</p> <p style="MARGIN: 0px">Case Study Example. . 660</p> <p style="MARGIN: 0px">Brokered Authentication&nbsp; 661</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 661</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 662</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 663</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 665</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 665</p> <p style="MARGIN: 0px">Case Study Example. . 666</p> <p style="MARGIN: 0px">CHAPTER 21: Transformation Patterns&nbsp; .&nbsp; . . . 669</p> <p style="MARGIN: 0px">Data Model Transformation&nbsp; 671</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 671</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 672</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 673</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 674</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 674</p> <p style="MARGIN: 0px">Case Study Example. . 677</p> <p style="MARGIN: 0px">Data Format Transformation&nbsp; . . . 681</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 681</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 681</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 683</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 683</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 683</p> <p style="MARGIN: 0px">Case Study Example. . 685</p> <p style="MARGIN: 0px">Protocol Bridging . 687</p> <p style="MARGIN: 0px">Problem&nbsp; .&nbsp; . . . 687</p> <p style="MARGIN: 0px">Solution&nbsp; .&nbsp; . . . 688</p> <p style="MARGIN: 0px">Application.&nbsp; .&nbsp; 688</p> <p style="MARGIN: 0px">Impacts&nbsp; .&nbsp; . . . 690</p> <p style="MARGIN: 0px">Relationships.&nbsp; . . . 690</p> <p style="MARGIN: 0px">Case Study Example. . 692</p> <p style="MARGIN: 0px">PART V: SUPPLEMENTAL</p> <p style="MARGIN: 0px">CHAPTER 22: Common Compound Design Patterns . . . 697</p> <p style="MARGIN: 0px">“Compound” vs. “Composite”&nbsp; . . . 698</p> <p style="MARGIN: 0px">Compound Patterns and Pattern Relationships&nbsp; .&nbsp; . . 698</p> <p style="MARGIN: 0px">Joint Application vs. Coexistent Application.&nbsp; .&nbsp; . . . . 699</p> <p style="MARGIN: 0px">Compound Patterns and Pattern Granularity&nbsp; .&nbsp; . . . . 700</p> <p style="MARGIN: 0px">Orchestration.&nbsp; 701</p> <p style="MARGIN: 0px">Enterprise Service Bus&nbsp; . 704</p> <p style="MARGIN: 0px">Service Broker&nbsp; 707</p> <p style="MARGIN: 0px">Canonical Schema Bus&nbsp; . 709</p> <p style="MARGIN: 0px">Official Endpoint . . 711</p> <p style="MARGIN: 0px">Federated Endpoint Layer&nbsp; . 713</p> <p style="MARGIN: 0px">Three-Layer Inventory.&nbsp;&nbsp;&nbsp; 715</p> <p style="MARGIN: 0px">CHAPTER 23: Strategic Architecture Considerations. . 717</p> <p style="MARGIN: 0px">Increased Federation&nbsp; . 718</p> <p style="MARGIN: 0px">Increased Intrinsic Interoperability&nbsp; . . 721</p> <p style="MARGIN: 0px">Increased Vendor Diversification Options.&nbsp; . 723</p> <p style="MARGIN: 0px">Increased Business and Technology Alignment.&nbsp; .&nbsp; . 725</p> <p style="MARGIN: 0px">Increased ROI&nbsp; . 727</p> <p style="MARGIN: 0px">Increased Organizational Agility&nbsp;&nbsp; 728</p> <p style="MARGIN: 0px">Reduced IT Burden. 729</p> <p style="MARGIN: 0px">CHAPTER 24: Principles and Patterns at the</p> <p style="MARGIN: 0px">U.S. Department of Defense&nbsp; . 731</p> <p style="MARGIN: 0px">The Business Operating Environment (BOE)&nbsp; .&nbsp; . . . . 733</p> <p style="MARGIN: 0px">Principles, Patterns, and the BOE&nbsp; . . 734</p> <p style="MARGIN: 0px">Incorporation of Information Assurance (IA)&nbsp; . . 736</p> <p style="MARGIN: 0px">Adherence to Standards&nbsp; . 736</p> <p style="MARGIN: 0px">Data Visibility, Accessibility, and Understandability to</p> <p style="MARGIN: 0px">Support Decision Makers&nbsp; 736</p> <p style="MARGIN: 0px">Loosely Coupled Services&nbsp;&nbsp;&nbsp; 736</p> <p style="MARGIN: 0px">Authoritative Sources of Trusted Data&nbsp;&nbsp; 737</p> <p style="MARGIN: 0px">Metadata-Driven Framework for Separation from</p> <p style="MARGIN: 0px">Technical Details&nbsp; . 737</p> <p style="MARGIN: 0px">Support Use of Open Source Software&nbsp; . . . 738</p> <p style="MARGIN: 0px">Emphasize Use of Service-Enabled Commercial</p> <p style="MARGIN: 0px">Off-the-Shelf (COTS) Software&nbsp; . 738</p> <p style="MARGIN: 0px">Participation in the DoD Enterprise&nbsp;&nbsp; 738</p> <p style="MARGIN: 0px">Support Mobility – Users &amp; Devices&nbsp; . . 738</p> <p style="MARGIN: 0px">The Future of SOA and the DoD&nbsp;&nbsp; 739</p> <p style="MARGIN: 0px">SOADoD.org&nbsp; . . 739</p> <p style="MARGIN: 0px">PART VI: APPENDICES</p> <p style="MARGIN: 0px">APPENDIX A: Case Study Conclusion&nbsp; 743</p> <p style="MARGIN: 0px">Cutit Saws Ltd.&nbsp; 744</p> <p style="MARGIN: 0px">Alleywood Lumber Company&nbsp; 744</p> <p style="MARGIN: 0px">Forestry Regulatory Commission (FRC)&nbsp; . . . 745</p> <p style="MARGIN: 0px">APPENDIX B: Candidate Patterns&nbsp; . . 747</p> <p style="MARGIN: 0px">APPENDIX C: Principles of Service-Orientation&nbsp; . . 749</p> <p style="MARGIN: 0px">Standardized Service Contract&nbsp;&nbsp; . 751</p> <p style="MARGIN: 0px">Service Loose Coupling&nbsp;&nbsp;&nbsp; 753</p> <p style="MARGIN: 0px">Service Abstraction . 755</p> <p style="MARGIN: 0px">Service Reusability . 756</p> <p style="MARGIN: 0px">Service Autonomy . . 758</p> <p style="MARGIN: 0px">Service Statelessness&nbsp; . 760</p> <p style="MARGIN: 0px">Service Discoverability&nbsp; 762</p> <p style="MARGIN: 0px">Service Composability&nbsp; 764</p> <p style="MARGIN: 0px">APPENDIX D: Patterns and Principles</p> <p style="MARGIN: 0px">Cross-Reference&nbsp; . . . 767</p> <p style="MARGIN: 0px">APPENDIX E: Patterns and Architecture Types</p> <p style="MARGIN: 0px">Cross-Reference&nbsp; . . . 775</p> <p style="MARGIN: 0px">About the Author&nbsp; . . . 783</p> <p style="MARGIN: 0px">About the Contributors &nbsp;&nbsp;. 784</p> <p style="MARGIN: 0px">Index of Patterns&nbsp; . . . 791</p> <p style="MARGIN: 0px">Index&nbsp; . 795</p> </div>

Managementboek Top 100

Rubrieken

Populaire producten

    Personen

      Trefwoorden

        SOA Design Patterns