"...Service-Oriented Architecture (SOA) is a component model that inter-relates an application's different functional units, called services, through well-defined interfaces and contracts between these services. The interface is defined in a neutral manner that should be independent of the hardware platform, the operating system, and the programming language in which the service is implemented. This allows services, built on a variety of such systems, to interact with each other in a uniform and universal manner....."
From this, it make me linked with the client side design pattern- Business Deligate and endpoint design pattern- service broker. which design pattern is fit in this SOA architecture and good for building multiple web services in different systems and interact with each other?
I'd like to hear other expert's explaination and opinion here.
[ January 24, 2006: Message edited by: Helen Li ] [ January 24, 2006: Message edited by: Helen Li ]
Sun has an article saying Service-Oriented Architecture (SOA) is a new concept for legacy enterprise integration and development. SOA and web services are two different things, but web services are the preferred standards-based way to realize SOA.
So my question is really how to apply the webservice design patterns to realize the SOA architecture in the real life. i.e, an enterprise could expose multiple interactive web services and each service may built on different system, what design patters should we use to design those web services to make them fit the SOA architecture? (Service-Broker? Business-Delegate?) My company is going to do the merger integration with other company and will expose some webservies to them soon, I am just think in ahead for the possible design issue.
SOA is an architectural trend that aims at building software infrastructures whose primary goal is to share their services. Web Services are actually one way of concretely implementing SOA. There are other solutions for achieving SOA (Jini, etc).
Section 10 of the exam objectives enumerate a list of design patterns that are usually used in web services solutions:
business delegate, service locator, and/or proxy client-side design patterns and the adapter, command, Web service broker, and/or fa�ade server-side patterns.
So yes, service broker and business delegate are some of the design patterns that you could use in a web service solution. [ January 26, 2006: Message edited by: Valentin Crettaz ]