SOA Magazine IV 01.2015

from the rest based on their past good / bad experiences. This kind of scenario often
leads to the most disparate opinions such as: “BPEL just doesn’t work at all and its use
implies a terrible danger for the client, we’ll be better off by using exclusively a Service
Bus”. Just imagine the turmoil an statement like this can produce, especially when
pronounced by an “expert” with a long track record in integration projects.
But is this controversy really just a matter of perception, past-experience, or even posttraumatic
stress disorder We’ve already dived enough into the history, so let’s have a look
now at some other kind of facts.
SOA Design Patterns
We saw in the past section how much the products have matured over time. At the same time, SOA as a
methodology has also been evolving and maturing through a series of contributions from industry
leaders, standards organizations, academics, professionals, architects and technology enthusiasts.
As a result of this contributions, we have a well identified set of SOA Design Patterns: proven solutions
to common problems.
NOTE:
*If you want to know more about SOA Design Patterns, make sure to visit the following site for a
thorough explanation:
http://www.soapatterns.org/
Here we’ll have a look at some of these patterns and whether they are more suitable to be applied by
the utilization of BPEL and/or Service Bus:
SOA Design Pattern BPEL OSB
Data Model Transformation X x
Data Format Transformation
x
State Repository
X
Rules Centralization X x
Process Abstraction
X
Process Centralization
X
Asynchronous Queuing X x
Intermediate Routing
x
Event-Driven Messaging X x
Protocol Bridging
x
Atomic Service Transaction X
Compensating Service Transaction X
Reliable Messaging
x
Policy Centralization
x
Copyright © 2015 | All Rights Reserved SOA Magazine IV 8