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 91
Pagina
... result, the time and effort required to automate new or changed business processes is correspondingly reduced because development projects can now be completed with significantly less custom development effort (Figure 3.32). Figure 3.32 ...
... result, the time and effort required to automate new or changed business processes is correspondingly reduced because development projects can now be completed with significantly less custom development effort (Figure 3.32). Figure 3.32 ...
Pagina
... result in direct or indirect consumer coupling . Figure 7.16 shows that when the service contract is technology ... resulting contract - to - functional coupling can be imposed on consumers . This can be an indirect form of negative ...
... result in direct or indirect consumer coupling . Figure 7.16 shows that when the service contract is technology ... resulting contract - to - functional coupling can be imposed on consumers . This can be an indirect form of negative ...
Pagina
... results based on the variance of the sub-class implementations. This is known as polymorphism. Because inheritance does not exist in service-orientation, this form of polymorphism is also not applied to individual ... result of naming.
... results based on the variance of the sub-class implementations. This is known as polymorphism. Because inheritance does not exist in service-orientation, this form of polymorphism is also not applied to individual ... result of naming.
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