WSSOA英文版培訓课件PPT第课extension.pptVIP

BUPTSSE SOA principles practice Lecture 7  Web Services and Contemporary SOA Agenda SOA Basic SOA Concepts WS-Reliability WS-Coordination WS-AtomicTransactions WS-BusinessActivity SOA Basic Myths about SOA SOA = Web Services Wrapping Services over Applications yields services SOA is a technology issue Shared Semantics is trivial SOA needs fully standardized mechanisms SOA can be done at an application level SOA can be implemented just by bringing an ESB How services encapsulate logic(1) To retain their independence, services encapsulate logic within a distinct context. This context can be specific to a business task, business entity, or some other logical grouping. The concern addressed by a service can be small or large. Therefore, the size and scope of the logic represented by the service can vary. Further, service logic can encompass the logic provided by other services. In this case, one or more services are composed into a collective. How services encapsulate logic(2) How services relate(1) Within SOA, services can be used by other services or other programs. This awareness is achieved through the use of service descriptions. A service description in its most basic format establishes the name of the service and the data expected and returned by the service. For services to interact and accomplish something meaningful, they must exchange information. How services relate(2) How services communicate(1) After a service sends a message on its way, it loses control of what happens to the message thereafter. That is why we require messages to exist as independent units of communication. This means that messages, like services, should be autonomous. To that effect, messages can be outfitted with enough intelligence to self-govern their parts of the processing logic. How services communicate How services are designed(1) Much like object-orientation service-orientation has become a distinct design approach which introduces commonly accepted pr