IT's Conundrum: Dealing With Data in SOA

Loraine Lawson

Johan den Haan, the head of research and development at Mendix and author of the blog The Enterprise Architect, recently pointed out that there's precious little written about SOA and data:

When reading these stories I mostly ask myself: Where is the data?

An astute question -- and a timely one, since DM Review just published an article by a database engineer addressing just this issue.

The writer -- Derek Wilson -- is a database engineer for Repubic Mortgage Insurance Company, based in North Carolina. Wilson writes that many customer data integration (CDI) projects are just too darn huge. They try to merge data together from all the source systems and see this as something that must be completed before the system is ready to do real work, like building a production process or application that actually uses the data.

He sees two problems with this:

  1. It's really hard and complicated. So it takes a long time.
  2. Since it takes so long, you take a hit on the ROI.

Couple the two and you've got a massive project that no one wants to fund.

Instead, he suggests a "build-and-ready" approach, which instead takes on data integration on as an-needed basis. You look at your end goal for the data, map to the source systems for that data, and build the web service to encapsulate the business logic needed to process the data.

You can either build your services as part of a specific, business-initiated customer data integration project, and include the cost of creating the service into the project, or you can build them as stand-alone IT projects, but develop them whenever you have to modify an application anyway.

What's brilliant about this approach, at least from an executive viewpoint, is that solves the problems Wilson mentioned, plus two more problems:

  1. How to align services with business goals, because services will be tied to business projects or application lifecycle.
  2. How to fund the services. In one case, you bill the business. In the other, it would be absorbed by IT, though IT would also be able to reap the benefits by demonstrating agility and possibly helping to leverage the the new integrated data as the source data for a new application, according to Wilson.

If you're looking for something more detailed, you should also read den Haan's full post, "Data Sharing in a Service-Oriented Environment." He's an enterprise architect, writing for other EAs, so his discussion -- and the resources he references -- are great reads for technologists struggling with the nitty gritty of data and SOA.

Add Comment      Leave a comment on this blog post

Post a comment





(Maximum characters: 1200). You have 1200 characters left.




Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.