Does SOA Solve Integration?

Service-Oriented Architecture Diagram

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

Is the Lack of SOA Talent Killing Cloud Computing?

Understand the Value of SOA or Fail

There is the thought about cloud computing to be this wonderful innovation that will solve all of world’s IT issues. The truth is that you’re still doing computing. You’re still keeping stuff, still processing stuff, still placing info in databases. This means– Dare I say it?– you have to put some architectural forethought around cloud computing.

The absence of an architecture– normally, the lack of a SOA– is a certainty for failure on the planet of cloud computing. An architecture offers the structure needed to harmonize your existing venture IT assets with the emerging world of cloud computing. Many who take advantage of clouds, PaaS, IaaS, or SaaS, understand the predicament and rapidly turn to basic architecture and planning … only to find that those ‘in the know’ are nowhere to be discovered.

Excellent SOA architects are a rare species. The trend is to take advantage of whatever the next magical and hyped technology is in the hopes that nobody will see that the existing architecture is a big mess, and the addition of cloud computing resources will just make it messier.

Making issues worse are the varieties of SOA innovation vendors who have incorrectly position their technology as “cloud computing innovation,” when they ought to be concentrated on SOA to bring about successful cloud computing. There is a substantial distinction. This supplier hype has actually just contributed to confusion around both the ideas of cloud computing and SOA. Throwing innovation at problems that actually require stronger architectural thinking and designing from the start.

Skilled SOA are bound to increase as cloud computing explodes.

Skilled SOA