1 / 13

Introduction to Service-Oriented Architecture

Introduction to Service-Oriented Architecture. Outline. Definition Features Examples of SOA Web Service Standards Example Pros and Cons Integration with Previous Works Issues. Definition.

ima
Download Presentation

Introduction to Service-Oriented Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction toService-Oriented Architecture

  2. Outline • Definition • Features • Examples of SOA • Web Service • Standards • Example • Pros and Cons • Integration with Previous Works • Issues

  3. Definition • A service is a unit of work done by a service provider to achieve desired end results for a service consumer • Results of a service are usually the change of state for the consumer or the provider • Let experts (providers) do the work for us (consumers) Providers Different quality of service Consumer

  4. Definition (cont.) • Webopedia:“An application architecture in which all functions, or services, are defined using a description language and have invokable interfaces that are called to perform business processes” • SOA is an architectural style whose goal is to achieve loose coupling among interacting software agents

  5. Features • Distributed • Components are distributed in the network • Loosely coupled • We can switch components according to our need as long as they implement the same interface • Open standard • Web Service standard • Easy integration even if implemented in different platforms • Process centric • Analysis the process of a specific task • Divide it to service interfaces

  6. Examples of SOA • CORBA? • CORBA software from different vendors may not always interoperate at all levels • DCOM? • Windows-based solution only • Web Service? • XML-based protocols that are lightweight and simple

  7. Web Service Standards • XML • Document format • HTTP • Transport layer protocol • SOAP • For message exchange • WSDL • Interface description • UDDI • Registration and discovery

  8. WSDL Example <message name="GetEndorsingBoarderRequest"> <part name="body" element="esxsd:GetEndorsingBoarder"/> </message><message name="GetEndorsingBoarderResponse"> <part name="body" element="esxsd:GetEndorsingBoarderResponse"/> </message> <portType name="GetEndorsingBoarderPortType"> <operation name="GetEndorsingBoarder"> <input message="es:GetEndorsingBoarderRequest"/> <output message="es:GetEndorsingBoarderResponse"/> <fault message="es:GetEndorsingBoarderFault"/> </operation> </portType>

  9. SOAP Messages SOAP resquest <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/“ SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body> <m:GetEndorsingBoarder xmlns:m="http://namespaces.snowboard-info.com"> <manufacturer>K2</manufacturer> <model>Fatbob</model> </m:GetEndorsingBoarder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> SOAP response <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body><m:GetEndorsingBoarderResponse xmlns:m="http://namespaces.snowboard-info.com"><endorsingBoarder>Chris Englesmann</endorsingBoarder> </m:GetEndorsingBoarderResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

  10. Pros Standard-based Loose coupling leads to increased modularity and flexibility Reduces integration costs Cons Immature Some vendor solutions are single-vendor approaches which conflict with the open standards-based vision of Web Services Pros And Cons of Web Service Programming Model

  11. Integration with Our Previous Work 3rd Party Services Dfdf IP Phone … Video Streaming APPs Accounting Service Web Service Interface Logging Service Task Switching RMI Roaming H.264 SW/HWComponents MPEGII VoIP RMI Streaming Security Services To make integration easier

  12. Integration Issues • Programming Model • Previous works are based on Java • Client applications should interoperate with our services through web service interfaces • Performance • SOAP message serialization downgrades performance

  13. Future Work • Model Definition • RMI Roaming + RMI Streaming • Integration with other works • Any possibilities?

More Related