Available:*
Library | Item Barcode | Call Number | Material Type | Item Category 1 | Status |
---|---|---|---|---|---|
Searching... | 30000010202545 | TK5105.88813 E744 2009 | Open Access Book | Book | Searching... |
On Order
Summary
Summary
" SOA Design Patterns is an important contribution to the literature and practice
of building and delivering quality software-intensive systems."
Author Notes
Thomas Erl is a best-selling IT author and founder of CloudSchool.com (tm) and SOASchool.com ®. Thomas has been the world's top-selling service technology author for over five years and is the series editor of the Prentice Hall Service Technology Series from Thomas Erl ( www.servicetechbooks.com ), as well as the editor of the Service Technology Magazine ( www.servicetechmag.com ). With over 175,000 copies in print world-wide, his eight published books have become international bestsellers and have been formally endorsed by senior members of major IT organizations, such as IBM, Microsoft, Oracle, Intel, Accenture, IEEE, HL7, MITRE, SAP, CISCO, HP, and others.
Four of his books, Cloud Computing: Concepts, Technology & Architecture, SOA Design Patterns, SOA Principles of Service Design, and SOA Governance, were authored in collaboration with the IT community and have contributed to the definition of cloud computing technology mechanisms, the service-oriented architectural model and service-orientation as a distinct paradigm. Thomas is currently working with over 20 authors on several new books dedicated to specialized topic areas such as cloud computing, Big Data, modern service technologies, and service-orientation. As CEO of Arcitura Education Inc. and in cooperation with CloudSchool.com (tm) and SOASchool.com ®, Thomas has led the development of curricula for the internationally recognized SOA Certified Professional (SOACP) and Cloud Certified Professional (CCP) accreditation programs, which have established a series of formal, vendor-neutral industry certifications. Thomas is the founding member of the SOA Manifesto Working Group and author of the Annotated SOA Manifesto ( www.soa-manifesto.com ). He is a member of the Cloud Education & Credential Committee, SOA Education Committee, and he further oversees the SOAPatterns.org and CloudPatterns.org initiatives, which are dedicated to the on-going development of master pattern catalogs for service-oriented computing and cloud computing. Thomas has toured over 20 countries as a speaker and instructor for public and private events, and regularly participates in international conferences, including SOA, Cloud + Service Technology Symposium and Gartner events. Over 100 articles and interviews by Thomas have been published in numerous publications, including the Wall Street Journal and CIO Magazine.Excerpts
Excerpts
Foreword The entire history of software engineering can be characterized as one of rising levels of abstraction. We see this in our languages, our tools, our platforms, and our methods. Indeed, abstraction is the primary way that we as humans attend to complexity--and software-intensive systems are among the most complex artifacts ever created. I would also observe that one of the most important advances in software engineering over the past two decades has been the practice of patterns. Patterns are yet another example of this rise in abstraction: A pattern specifies a common solution to a common problem in the form of a society of components that collaborate with one another. Influenced by the writings of Christopher Alexander, Kent Beck and Ward Cunningham began to codify various design patterns from their experience with Smalltalk. Growing slowly but steadily, these concepts began to gain traction among other developers. The publication of the seminal book Design Patterns by Erich Gamma, John Vlissides, Ralph Johnson, and Richard Helm marked the introduction of these ideas to the mainstream. The subsequent activities of the Hillside Group provided a forum for this growing community, yielding a very vibrant literature and practice. Now the practice of patterns is very much mainstream: Every well-structured software-intensive system tends to be full of patterns (whether their architects name them intentionally or not). The emerging dominant architectural style for many enterprise systems is that of a service-oriented architecture, a style that at its core is essentially a message passing architecture. However, therein are many patterns that work (and anti-patterns that should be avoided). Thomas' work is therefore the right book at the right time. He really groks the nature of SOA systems: There are many hard design decisions to be made, ranging from data-orientation to the problems of legacy integration and even security. Thomas offers wise counsel on each of these issues and many more, all in the language of design patterns. There are many things I like about this work. It's comprehensive. It's written in a very accessible pattern language. It offers patterns that play well with one another. Finally, Thomas covers not just the technical details, but also sets these patterns in the context of economic and other considerations. SOA Design Patterns is an important contribution to the literature and practice of building and delivering quality software-intensive systems. --Grady Booch, IBM Fellow September, 2008 (c) Copyright Pearson Education. All rights reserved. Excerpted from SOA Design Patterns by Thomas Erl All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.Table of Contents
Foreword | p. xxxvii |
Chapter 1 Introduction | p. 1 |
1.1 Objectives of this Book | p. 4 |
1.2 Who this Book is For | p. 4 |
1.3 What this Book Does Not Cover | p. 4 |
Topics Covered by Other Books | p. 4 |
Web Service and Rest Service Design Patterns | p. 5 |
SOA Standardization Efforts | p. 5 |
1.4 Recommended Reading | p. 6 |
1.5 How this Book is Organized | p. 7 |
Part I Fundamentals | p. 8 |
Part II Service Inventory Design Patterns | p. 8 |
Part III Service Design Patterns | p. 8 |
Part IV Service Composition Design Patterns | p. 9 |
Part V Supplemental | p. 10 |
Part VI Appendices | p. 10 |
1.6 Symbols, Figures, Style Conventions | p. 11 |
Symbol Legend | p. 11 |
How Color is Used | p. 11 |
Data Flow and Directionality Conventions | p. 11 |
Pattern Documentation Conventions | p. 11 |
1.7 Additional Information | p. 11 |
Updates, Errata, and Resources (www.soabooks.com) | p. 11 |
Visio Stencil (www.soabooks.com) | p. 12 |
Community Patterns Site (www.soapatterns.org) | p. 12 |
Master Glossary (www.soaglossary.com) | p. 12 |
Supplementary Posters (www.soaposters.com) | p. 12 |
The SOA Magazine (www.soamag.com) | p. 12 |
Referenced Specifications (www.soaspecs.com) | p. 12 |
Notification Service | p. 13 |
Contact the Author | p. 13 |
Chapter 2 Case Study Background | p. 15 |
2.1 Case #1 Background: Cutit Saws Ltd | p. 17 |
History | p. 18 |
Technical Infrastructure and Automation Environment | p. 18 |
Business Goals and Obstacles | p. 18 |
2.2 Case #2 Background: Alleywood Lumber Company | p. 19 |
History | p. 19 |
Technical Infrastructure and Automation Environment | p. 20 |
Business Goals and Obstacles | p. 20 |
2.3 Case #3 Background: Forestry Regulatory Commission (FRC) | p. 21 |
History | p. 21 |
Technical Infrastructure and Automation Environment | p. 21 |
Business Goals and Obstacles | p. 22 |
Part I Fundamentals | |
Chapter 3 Basic Terms and Concepts | p. 25 |
Purpose of this Introductory Chapter | p. 26 |
3.1 Architecture Fundamentals | p. 26 |
A Classic Analogy for Architecture and Infrastructure | p. 27 |
Technology Architecture | p. 27 |
Technology Infrastructure | p. 30 |
Software Program | p. 32 |
Relationship to Design Framework | p. 33 |
3.2 Service-Oriented Computing Fundamentals | p. 35 |
Service-Oriented Computing | p. 35 |