https://training-course-material.com/index.php?action=history&feed=atom&title=SOA_ConceptsSOA Concepts - Revision history2026-04-15T00:12:22ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=SOA_Concepts&diff=9672&oldid=prevBernard Szlachta: /* ESB */2013-03-21T11:24:37Z<p><span class="autocomment">ESB</span></p>
<p><b>New page</b></p><div>{{Cat|SOA|10}}<br />
{{Soa Links}}<br />
<br />
*Service<br />
*ESB<br />
*Loose Coupling<br />
*Policies and Processes<br />
*Web Services<br />
*SOA Strategy<br />
*Governance<br />
<br />
== Service ==<br />
A service is a piece of self-contained business functionality. The functionality might be simple (storing or retrieving customer data), or complex (a business process for a customer’s order). Because services concentrate on the business value of an interface, they bridge the business/IT gap.<br />
<br />
<br />
== ESB ==<br />
* ESB is the '''infrastructure''' that enables high interoperability between distributed systems for services.<br />
* It makes it easier to distribute business processes over multiple systems using different platforms and technologies.<br />
* TCP network + DNS may be consider a type of ESB<br />
<br />
==Loose Coupling==<br />
*Concept of reducing system dependencies.<br />
*Minimize the effects of modifications and failures. <br />
*Price for loose coupling: complexity.<br />
*Loosely coupled distributed systems are harder to develop, maintain, and debug.<br />
<br />
<br />
==Policies and Processes==<br />
You need clearly defined roles, policies, and processes<br />
*service lifecycle<br />
*implementing model-driven service development<br />
*set up several processes for distributed software development.<br />
*agile project management<br />
<br />
<br />
== Web Services ==<br />
* Web Services are one possible way of realizing the technical aspects of SOA<br />
* Web Service can be based on SOAP or REST<br />
<br />
==Governance and Management support==<br />
*Central team that will determine general aspects of your specific SOA. <br />
*The ultimate goal is decentralization <br />
*Right people (large systems are different from small systems)<br />
*Requirements driven development<br />
*You need support from the CEO and CIO. SOA is a strategy that affects the company as a whole.<br />
<br />
<br />
==Technical Concept of SOA==<br />
*Services<br />
*Interoperability<br />
*Loose coupling<br />
<br />
<br />
==SOA Ingredients==<br />
*Infrastructure<br />
*Architecture<br />
*Processes<br />
*Governance<br />
<br />
<br />
==SOA Terminology==<br />
*A '''provider''' is a system that implements a service (a business functionality) so that other systems can call it.<br />
*A '''consumer''' is a system that calls a service (uses a provided service).<br />
*Other names: requestor, client, server....<br />
*'''A participant (AKA service agent) is either a provider or a consumer'''<br />
<br />
<br />
==SoaML Notation==<br />
[[File:Soa-soaml-notation1.png|300px]] [[File:Soa-soaml-notation2.png|450px]]<br />
<br />
<br />
==Another definition of SOA==<br />
SOA is an architectural paradigm <br />
* for dealing with business processes <br />
* distributed over a large landscape of existing and new<br />
* heterogeneous systems <br />
* that are under the control of different owners.<br />
<br />
==Different Perspective==<br />
[[File:Soa-different-perspective.png|350px]]<br />
<br />
<br />
== Questions ==<br />
*What are the three technical concepts of SOA?<br />
*What are the key ingredients of SOA?<br />
*Is SOA a technology?<br />
*What is the difference between services and web services?<br />
*Does SOA have to use Web Services?</div>Bernard Szlachta