SOA and Web services interface design principles, techniques, and standards
With the introduction of increasingly complex Web services over the last decade, there has been an explosion of interest in service-oriented architecture (SOA), a structural style whose goal is to achieve a coupling of interacting services - functionalities such as filling out an online application...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Burlington, MA : Oxford :
Morgan Kaufmann ; Elsevier Science [distributor]
2009.
|
| Colección: | The MK/OMG Press
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627988406719 |
Tabla de Contenidos:
- Front Cover; SOA and Web Services Interface Design: Principles, Techniques, and Standards; Copyright Page; Contents; Acknowledgments; CHAPTER 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-BAM1.5.5 Web Services Management-WSM; 1.5.6 Closing the SOA Loop; 1.6 The Benefits of SOA; CHAPTER 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; CHAPTER 3 Web Services and Other Service Types and Styles; 3.1 Web Services and SOAP; 3.2 ReST Style Services; 3.3 Legacy Services and API's; CHAPTER 4 Data, the Missing Link; 4.1 Data at Rest-Persistence; 4.2 Data in Motion-Messaged Context
- CHAPTER 5 Data Services5.1 A Single Data at Rest Data Source; 5.2 Multiple and Disparate Data at Rest Sources; 5.3 Resolving Data Impedance with Data Services; 5.4 CRUD-Based Data Services; CHAPTER 6 Transformation to Resolve Data Impedance; 6.1 Transformation; 6.2 Translation; 6.3 Aggregation; 6.4 Abstraction; 6.5 Rationalization; CHAPTER 7 The Service interface-a Contract; 7.1 Web Services Description Language-WSDL; 7.2 XML Schemas-XSD; 7.3 Extensible Markup Language; CHAPTER 8 Canonical Message Design; 8.1 The Message Is a Hierarchy; 8.2 Top-Down Canonical Message Design
- 8.2.1 Design Requirements8.2.2 Conceptual Message Design; 8.2.3 Logical Message Design; 8.2.4 Physical Message Design; 8.2.5 Create and Refine Message Schemas; 8.2.6 Create WSDL; 8.3 Model-Driven Interface Design; CHAPTER 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; CHAPTER 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; CHAPTER 11 XML Schema Design Patterns; 11.1 complexType Patterns
- 11.2 Global Declaration Patterns11.3 Local Declaration Patterns; 11.4 Reusable Schema Patterns; 11.5 substitutionGroup Patterns; CHAPTER 12 Schema Assembly and Reuse; 12.1 Considerations for Schema Reuse; 12.1.1 Identifying Service Interface Reuse Opportunities; 12.1.2 Interface Schema Granularity; 12.1.3 Designing the Interface Schema with Intent to Reuse; 12.2 Namespaces; 12.3 Schema Reuse by Reference and Assembly; 12.4 Limitations and Complexities; CHAPTER 13 The Interface and Change; 13.1 Schema Extension; 13.2 Schema Versioning; 13.3 Change and Capabilities of the ESB and WSM
- CHAPTER 14 Service Operations and Overloading
