Typically when organizations are thinking about migrating to an SOA, the data environment is not one of the top things on their mind. They are more focused on modeling their business processes and figuring out how to create reusable services out of them. That is rather unfortunate because the data plays a big part in driving the proper execution of those business processes. Additionally, the data environment of the typical large organization has a lot of issues that will only become more problematic in an SOA environment due to the more real-time and integrated nature of SOA-based applications. In some cases, trying to move to an SOA without first addressing the data issues is akin to trying to build a high-rise on top of a landfill--you're trying to build a complex structure on top of a weak foundation.
A couple of colleagues and I are writing an article for the June issue of SOA Web Services Journal that talks about creating a data strategy for an SOA to ensure that you have a proper data environment before jumping into your SOA transformation. This strategy addresses issues such as data governance, enterprise data models and standards, security, data quality, and data services. Keep an eye out for it. There's a lot of useful information in there. A lot of it is based on experiences from projects our firm's done with the large government agencies. I will post a link to the article here when they make it available online.
SOA, data integration
Subscribe to:
Post Comments (Atom)
Posts
1 comment:
I have been working on such an approach, using the federal Data Reference Model as a framework. Would be interested in your paper, but could not find it yet.
I will check back.
CES
Post a Comment