In SOA and Web Services Interface Design, data architecture guru James Bean teaches you how to design web service interfaces that are capable of being extended to accommodate ever changing business needs and promote incorporation simplicity. The book first provides an overview of critical SOA principles, thereby offering a basic conceptual summary. It then provides explicit, tactical, and real-world techniques for ensuring compliance with these principles. Using a focused, tutorial-based approach the book provides working syntactical examples - described by Web services standards such as XML, XML Schemas, WSDL and SOAP - that can be used to directly implement interface design procedures, thus allowing you immediately generate value from your efforts. In summary, SOA and Web Services Interface Design provides the basic theory, but also design techniques and very specific implementable encoded interface examples that can be immediately employed in your work, making it an invaluable practical guide to any practitioner in today's exploding Web-based service market.

Key Features

  • Provides chapters on topics of introductory WSDL syntax and XML Schema syntax, taking take the reader through fundamental concepts and into deeper techniques and allowing them to quickly climb the learning curve.
  • Provides working syntactical examples - described by Web services standards such as XML, XML Schemas, WSDL and SOAP - that can be used to directly implement interface design procedures.
  • Real-world examples generated using the Altova XML Spy tooling reinforce applicability, allowing you to immediately generate value from their efforts.
  • A companion website with all artwork and code examples accompanies the book (


Technology practitioners involved in the design and development of SOA services and service interfaces including enterprise and integration architects responsible for defining company information architecture, computer software engineers who research and develop vendor SOA-based applications, and business solutions architects.

Table of Contents

1. SOA – A Common Sense Definition 1.1 Origins of SOA 1.1.1 Technology Becomes a Commodity 1.1.2 Technology Becomes an Enabler 1.1.3 Technology Becomes a Transformer 1.2 A Definition for SOA 1.3 Consumers, Services, and Intermediaries 1.4 Messaging - The Means of Interaction between Consumer and Services 1.5 SOA Capabilities 1.5.1 The Enterprise Service Bus - ESB 1.5.2 The Service Registry and Repository - SRR 1.5.3 Business Process Management - BPM 1.5.4 Business Activity Monitoring - BAM 1.5.5 Web Services Management - WSM 1.5.6 Closing the SOA Loop 1.6 The Benefits of SOA 2. Core SOA Principles 2.1 Loose Coupling 2.2 Interoperability 2.3 Reusability 2.4 Discoverability 2.5 Governance 2.5.1 Design-Time Governance 2.5.2 Bind-Time Governance 2.5.3 Run-Time Governance 3. Web Services vs. other Types and Styles of Services 3.1 Web Services and SOAP 3.2 ReST Style Services 3.3 Legacy Services and API’s 4. Data – the Missing Link 4.1 Data at Rest – Persistence 4.2 Data in Motion – Messaged Context 5. Data Services 5.1 Multiple and Disparate Data at Rest Sources 5.2 Resolving Data Impedance with a Data Service 5.3 CRUD Based Services 6. Transformation to Resolve Data Impedance 6.1 Transformation 6.2 Translation 6.3 Aggregation 6.4 Abstraction 6.5 Rationalization 7. The Service Interface - the “Contract” 7.1 Web Services D


No. of pages:
© 2010
Morgan Kaufmann
Print ISBN:
Electronic ISBN:

About the editor

James Bean

James Bean is the President and CEO of the Relational Logistics Group. He is the author of the books: the "Sybase Client/Server EXplorer" © 1996 Coriolis Group Books and "XML Globalization and Best Practices" © 2001, and has written numerous magazine articles for technology journals. He is also the Chairman of the Global Web Architecture Group.

Affiliations and Expertise

CEO, Relational Logistics Group, Phoenix, Arizona, U.S.A.