Does SOA Solve Integration?

Cloud Service-Oriented Architecture (SOA)

The basic principles of service-oriented architecture are independent of vendors, products and technologies

“So did SOA resolve integration? No. However then once again, no one ever promised you that. As Neil observes, we’ll probably never see a ‘turnkey enterprise integration solution,’ but that’s probably an advantage – after all, organizations have various needs, and such an option would need an Orwellian-level of standardization.”

The fact of the issue is that SOA and integration are 2 various, but interrelated concepts. SOA is a means of doing architecture, where integration might be a result of that architecture. SOA does not set out to do integration, however it possibly a by-product of SOA. Baffled yet?




Truth-be-told integration is a deliberate technique, not a byproduct. Hence, you have to have an integration strategy and architecture that belongs of your SOA, and not simply a desired outcome.You’ll never get there, trust me.

 

The problem is that there are 2 architectural patterns at play right here.

First, is the goal to externalize both habits and information as sets of services that can be set up and reconfigured into options. That’s at the heart of SOA, and the integration typically takes place within the composite applications and procedures that are produced from the services.

Second, is the goal to duplicate info from source to target systems, ensuring that details is shared in between inconsistent applications or total systems, which the semantics are handled. This is the objective of integration, and was at the heart of the architectural pattern of EAI.

Plainly, integration is a purposeful action and thus needs to be dealt with within architecture, including SOA. Thus, SOA won’t fix your integration issues; you need to deal with those directly.

service-oriented architecture

Cloud Computing Types Reviews
Tell us If We Helped You