Over a million developers have joined DZone.

Top 10 SOA Pitfalls: Wrap-up

· Integration Zone

Build APIs from SQL and NoSQL or Salesforce data sources in seconds. Read the Creating REST APIs white paper, brought to you in partnership with CA Technologies.

The Top 10 SOA Pitfalls countdown hit #1 last week with Rik de Groot's post on "Ignoring culture when introducing SOA", time for a wrap-up.

Putting all pitfalls together in one simple 10 item list quickly reveals a grouping of types pitfalls. Number #1 and #2 are both related to organizational aspect. If the culture, mindset and attitude are not right, these are typically the pitfalls that a SOA endeavor may run in to. The next group covers the items #3 till #7, these are all related to architectural/design skills. And the last group, numbers #8 till #10, relates to implementation issues (although proper design could help to prevent these pitfalls from manifesting themselves). The complete Top 10 SOA pitfalls list is:

Implementation pitfalls

Architectural/design pitfalls Organizational pitfalls: It was great fun to compile this list with the four of us and it also helped us to get a sharper view on why SOA projects or programs are challenging and hard to complete succesfully. Hopefully you've learned a thing or two and are able to prevent or at least recognize the pitfalls in your day-to-day work. Thanks for having us, Rik de Groot, Viktor Grgic, Vincent Partington, and Gero Vermaas.

The Integration Zone is brought to you in partnership with CA Technologies.  Use CA Live API Creator to quickly create complete application backends, with secure APIs and robust application logic, in an easy to use interface.

Topics:

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}