SOA and Web Services Interface Design

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 Description Language – WSDL
   7.2 XML Schemas – XSD
   7.3 Extensible Markup Language - XML
   
   8. Canonical Message Design
   8.1 The message is a hierarchy
   8.2 Top-Down canonical message design
   8.3 Model Driven Interface Design
   
   9. The Enterprise Taxonomy
   9.1 Focus on Common Business Language for Discovery
   9.2 Broadening and extending the taxonomy
   9.3 Registry Entries and Discovery
   
   10. XML Schema Basics
   10.1 elements
   10.2 attributes
   10.3 simpleTypes
   10.4 complexTypes
   10.5 groups
   10.6 namespaces
   10.7 import, include
   
   11. XML Schema Design Patterns
   11.1 complexTypes
   11.2 Referencing Global Declarations
   11.3 Local Element Declarations
   11.4 Reusable Schemas Without Namespaces
   11.5 Reusing and Applying Namespaces
   11.6 Reusing and Applying Namespaces to Schema Assemblies
   11.7 Using substitutionGroups
   
   12. Schema Assembly and Reuse
   12.1 Namespaces
   12.2 Schema Reuse by Reference and Assembly
   12.3 Limitations and Complexities
   
   13. The Interface and Change
   13.1 Schema Extension
   13.2 Schema Versioning
   13.3 Change and Capabilities of the ESB and WSM
   
   14. Service Operations and Overloading
   14.1 Service Granularity
   14.2 Scoping of Service Operations
   14.3 Operations Overloading
   
   15. Selective Data Fragmentation
   15.1 Grouping Data by Expressed Affinity
   15.2 Avoiding a Complex or Non-Deterministic Content Model
   
   16. Update Transactions
   16.1 Update Transactions and State
   16.2 Request – Reply Message Exchange Patterns
   16.3 Complexities of Fire and Forget for Updates
   
   17. Fixed Length Transactions and Nulls
   
   18. Document Literal Interfaces
   
   19. Performance Analysis and Optimization Techniques
   19.1 Uniformity of Structure
   19.2 Navigation and Data Graphs
   19.3 Depth of Nesting
   19.4 Verbosity
   19.5 Abstract vs. Specific Cardinality
   19.6 To Validate or Not to Validate
   
   20. Error Definition and Handling
   
   A. Appendix
   A.1 Glossary and Abbreviations
   A.2 Web Services Standards
   A.3 Bibliography and References

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.

• 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.

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.