SOA Principles of Service DesignPrentice Hall, 18 jul 2007 - 608 pagina's The Definitive Guide to Service Engineering The key to succeeding with service-oriented architecture (SOA) is in comprehending the meaning and significance of its most fundamental building block: the service. It is through an understanding of service design that truly “service-oriented” solution logic can be created in support of achieving the strategic goals associated with SOA and service-oriented computing. Bestselling SOA author Thomas Erl guides you through a comprehensive, insightful, and visually rich exploration of the service-orientation design paradigm, revealing exactly how services should and should not be designed for real-world SOA.
|
Vanuit het boek
Resultaten 1-3 van 90
Pagina
... that describes how the service carries out its capabilities . • • Quality of Service Information - Meta data that describes service behavior , limitations , and interaction requirements . Figure 8.3 . Common types of service meta ...
... that describes how the service carries out its capabilities . • • Quality of Service Information - Meta data that describes service behavior , limitations , and interaction requirements . Figure 8.3 . Common types of service meta ...
Pagina
... information about resources (meta information) that we want to make available for discovery meta information to be accurately defined by those who understand the underlying resource the best meta information to be clearly documented by ...
... information about resources (meta information) that we want to make available for discovery meta information to be accurately defined by those who understand the underlying resource the best meta information to be clearly documented by ...
Pagina
... meta information been documented in plain English? 2. If yes, has functional meta information been clearly expressed as part of the service contract for discoverability purposes? 3. Has quality of service information been documented in ...
... meta information been documented in plain English? 2. If yes, has functional meta information been clearly expressed as part of the service contract for discoverability purposes? 3. Has quality of service information been documented in ...
Inhoudsopgave
Introduction | |
Appendix A Case Study Conclusion | |
Case Study | |
16 andere gedeelten niet getoond
Overige edities - Alles bekijken
Veelvoorkomende woorden en zinsdelen
agnostic services application associated automation business process Chapter composition members constraints contract design core service logic Cutit data models database defined definition delivery Denormalization dependencies design characteristics design paradigm design patterns design standards design-time document encapsulate enterprise enterprise architecture entity service environment establish existing Figure functional context granularity increased information hiding interface interoperability Inventory service Invoice Key Points legacy legacy system meta data meta information object-orientation operation overall platform proprietary quality of service represents result reusable services Run Lab Project runtime Service Abstraction Service Autonomy service capability service composition service design Service Discoverability service implementation service inventory blueprint Service Loose Coupling service models service profile service registry Service Reusability Service Statelessness service-orientation principles service-oriented analysis service-oriented architecture service-oriented computing service's solution logic specific Standardized Service Contract Summary of Key task service technical utility service WS-Addressing WS-BPEL WS-Policy WSDL XML schema