So, Ah...What About the Data?

Loraine Lawson

Every few months, I run across some post or article noting that SOA is great for application integration, but pondering how it can relate to data integration. The question is, can data be service-enabled in the same way SOA service-enables processes and functions?


This week, Joe McKendrick visits the issue on the heels of an ebizQ webcast he moderated. He writes that the webcast covered:

"an emerging approach, called data services, which ties into service oriented architecture (SOA) and creates a data abstraction layer that addresses the complexities seen across enterprise data environments."

I'm horrible about attending webinars -- I forget or am just too busy -- so I'm always grateful for a summary, transcript or a recast. And I'm particularly happy McKendrick decided to summarize this webcast, because it covers a widespread problem. You just don't see much about it.


What fascinates me about this is that I've seen some information about SOA and data integration and data services. I remember well over a year ago, David Linthicum shared how he'd studied data integration technology for an upcoming book and found problems with coupling the two. And I've seen occasional other references to data services and SOA, but it always seems theoretical.


During the webcast, McKendrick spoke with Ash Parikh, principal product marketing manager for Informatica. Parikh explains why this is an ongoing problem; he also discusses how he thinks it can be addressed. Step one: Pursue delivery of data services. Okay, no duh. The problem is you have to find a way to ensure the data services are delivering a consistent view of the data. (On a side note, some have suggested master data management, or MDM, could be the tool for making sure the data is consistent and clean for SOA.)


That's when Parikh gets into the more valuable information.


Technically, Parikh said, data service must be modular, reusable and leverage established technology standards. McKendrick quotes him as saying a data service:

"...enables access integration to right time data throughout the enterprise and across corporate firewalls. Data services create an abstraction layer to all analytical, operational information, and serves it up to other abstraction layers, which could be an [enterprise service bus]."

McKendrick's piece suggests to me something is finally shaking loose in the ongoing challenge of data services and SOA. I plan to go back and listen to the webcast, despite my aversion to anything resembling a PowerPoint slide.


In the meantime, I'd love to hear from anyone with more information on data integration, data services and SOA.

Subscribe to our Newsletters

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


More from Our Network
Add Comment      Leave a comment on this blog post
Jul 31, 2008 9:00 AM Robere Eve Robere Eve  says:
Loraine - Yes, data can be service-enabled in the same way SOA service-enables business processes and transactions.David Besemer provides a really good desciption of data services in "An Implementor's Guide to SOA" which can be freely downloaded at http://www.soaguidebook.com/chapters.html#chapter2 He nicely contrasts data and transaction services, clarifying key issues from a service design point of view. From a governance point of view, typical SOA design and runtime governance needs to be enhanced with data governance. But in the long run, governing clearly defined, loosely-coupled, abstracted data services is a lot easier than governing siloed, old school FTPs and ELT scripts. - Bob Eve Reply
Jul 31, 2008 9:35 AM Rob Eamon Rob Eamon  says:
IMO, services that only provide access to data, without functional operations that provide some sort of capability, is the wrong focus. The important thing about service orientation is doing something, not just reading or writing data. A service wrapper around data access is a data oriented approach, not an SO approach.Presumably, one reads data in order to do something with it. The reading and the doing should be part of the same service, IMO. Segregating services by data vs. transaction is fundamentally flawed IMO. Reply

Post a comment





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




Subscribe Daily Edge Newsletters

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

Subscribe Daily Edge Newsletters

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