In service-oriented architecture (SOA), the point is to make life easier for both the
enterprise which will use the finished system and the IT specialists who have to create the
SOA. Thus, when we speak of SOA integration, it refers to integration of the SOA into the
business or organizational environment of the enterprise.
Many decision-makers doubt the effectiveness and efficiency that SOA integration can bring,
and may be tempted to initiate the creation of a new system from the ground up. This
problem is more common nowadays due to the spate of acquisitions and mergers of
organizations, which results in combination as well of their respective IT systems if
possible. And it can be possible if SOA is to be applied well.
To create an enterprise-wide SOA integration solution, the SOA system has to be planned
well with an eye towards retaining the flexibility of individual components even before any
foreseen or unforeseen changes occur (like even before the organization gets snatched up by
a bigger player in an acquisition.) It is paramount that the SOA integration be built-in
the overall system so that renovation later on becomes easier for the IT team.
The enterprise also has to use an SOA that will permit interoperability – otherwise, the
system will become unmanageable, and perhaps even unusable. Interoperability is a basic
element in full SOA integration because without it, you might as well build a new system
To assure interoperability, your SOA might be based on Web services which are actually an
array of implementation technologies. Some say adoption of Web services could really be the
best practice for interoperability right now.