| Title: |
SOA Reference Model – Part 2 – the Flexible Service Runtime |
| Author: |
John Cheesman, Georgios Ntinolazos |
| Publication Date: |
10 June 2004 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
This article builds on the SOA reference model foundation described in the March 2004 CBDI Journal. It examines further the SOA concepts with a particular focus on the patterns and software roles needed for flexible coupling in the service runtime. We compare these patterns with existing technology-focused approaches for EJB, .NET and Web Services, and provide a systems integration scenario to support the flexible coupling requirement. |
| Backgrounder: |
SOA is the current state of evolution of best practice in the organization and architecture of enterprise systems. As the information systems industry moves forward we have progressed from monolithic systems, to client-server, to more generalized distributed n-tier systems using object request brokers (ORBs). Within this context we have also needed to provide solutions to infrastructure requirements such as transaction support, security and so on – enter the container model, supported by both the J2EE architecture and .NET, where business logic is kept separate from technology platform provision of infrastructure services. For example, the container takes care of managing the transaction and you take care of the business functionality.
Where SOA moves the agenda on is in shifting the emphasis from tightly-coupled, fine-grain distribution of application design elements to more loosely-coupled, coarser-grain distribution of software services supporting business processes. This increases software provision flexibility and creates a more direct link to business process change. Although many of the underlying themes and principles are common, the method and level of applying them is significantly different.
Loose-coupling has many connotations, so in this context we should perhaps use the term “flexible-coupling”. Specifically, when connecting service consumers and providers together we want to be able to provide strong, well-defined and stable connections, but also flexible, readily reconfigurable connections. This means that existing service consumers and providers can be assembled together unchanged to obtain business solutions in different technical environments and with different operational constraints
|
| Report Size: |
11 Pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home