Ronan Bradley's FinanceTech Directions

Ronan Bradley

Data: The heart of SOA

user-pic
Vote 0 Votes

There has been a spate of customer success stories emerging over the last few weeks - one feature of these that is prominently highlighted is the focus on data. This should hardly be surprising given a major component of all integration problems (once you get beyond technology integration) is bridging between the data models. Within a SOA, the data models built are then exposed through the service definitions. The requesting applications must either formulate the request using the data model of the service provider or more commonly rely on an intermediary such as an ESB to bridge the gap (something I refer to as mediation).


Chief Application Architect Eric Peebles for the City of Chicago recently highlighted the role of data within SOA and he pointed out while speaking about why Chicago moved to SOA using iWay’s products:

city departments and even major citywide applications are separate islands of information about people, companies, land, and buildings. We needed a strategy to integrate these applications and data in order to drive business improvements more effectively.

There are two fundamental approaches to dealing with data integration within SOA: Build a global data model for your business which each connecting business unit must bridge into and out of in order to integrate with other units or build multiple data models. At their most extreme, there are major problems with each approach:

 Attempting to build a single global data model becomes harder as the size of the organization grows and the level of change increases. It requires an excellent understanding of the business at the start and an understanding of how change will impact upon it to successfully wire the data model for change. The approach of attempting to adopt a public standard is also not the solution (for instance FpML in financial services for derivatives) as there will significant divergences between the standard and what your business needs – it can be too complex, too simple or just plain wrong! That is not to say building a global data model is impossible – simply it is never as simple as it appears at the start!

 Allowing each unit to build their own data model and then providing bridging capabilities between each business unit. This builds cost and complexity into the integration layer which can slow down each project if the intermediary (such as an ESB) is not sufficiently powerful. It can also reduce the level of reuse between the business units of knowledge around building data models for your organization.


The solution is of course balance between the two approaches – and the precise balance will depend on the industry and the organization. For instance:

 If your architecture requires a central data exchange through which multiple organizations combine to complete business transactions, it may make sense to veer towards a global data model for this exchange.

 If your organization uses a lot of out sourcing or provides out-sourcing to other organizations, it may make sense to veer towards a per-unit data model as you will have limited control over the data model of the other parties.


Finally, the approach to building data models within a SOA context must be sensitive to the types of integration problems that need to be solved and specifically the data models that your model must integrate with. I have seen models which are theoretically perfect, but because of complexity and the mismatch between the model (exposed through service definitions) and what it needed to interact with where almost impossible to use. As with so much in integration, where possible keep it simple and build in the ability to change.

2 TrackBacks

TrackBack URL: http://www.ebizq.net/MT4/mt-tb.cgi/10563

I was pleased to see Ronan Bradley's post from the other day 'Data: The Heart of SOA.' I liked it so much I almost stole the title. In it, he talks about how data issues really are part and parcel Read More

Think Locally, Act Locally from Architected Information on July 29, 2006 10:57 PM

In Roads to SOA, Ronan Bradley wrote an interesting piece titled “Data: The Heart of SOA“. He hits the nail right on the head with this article. He writes … There are two fundamental approaches to dealing with data integration withi... Read More

3 Comments

| Leave a comment

What about information as a service or data virtualization? These are key concepts for data and SOA. See post...

http://blogs.ittoolbox.com/eai/business/archives/information-fabric-and-soa-9055

WHile data integration is one aspect to be considered in SOA, I strongly believe that new persisitence models have to be considered for SOA to scale. Relying on data flows that originate and end in the actual data sources will cripple most SOA deployments (and perhaps why most EII deployments suffer from poor performance and scalability - the slowest link dictates overall system health). Distibuted, in-memory caching/persistence models is certainly one effective way to deal with the distributed loosely coupled nature of SOA. Services deal with the operational subset of data that matters to them and can transact on it, without being bottlenecked by backend data sourced

Bharath,

I totally agree with your points on new persistence models: As SOA scales, it becomes essential that caching occurs in the middle - understanding all the usual issues about caching of data (synchronization etc) have to be handled. Caching will have to become an important capability provided by intermediary platforms such as ESBs - or at least plugged into those platforms.

Somewhat tangentially, I see the current interest in Enterprise Web2.0 potentially driving the same requirement ahead of SOA as a proliferation of RSS feeds will kill any back-end system attempting to cope with a 1,000 corporate desktops requesting the business intelligence reports at 5pm on Friday evening!

Ronan

Leave a comment

Recent posts from our Blogs

Eleven Indicted in Biggest Identity Theft Case
The Warehouse: Where Much Business Intelligence is Stored
BPM VIEWPOINT: Looking Behind the Curtain at the Magic of the Gartner BPM Magic Quadrant
Health IT Stimulus Check to Spend? Check out the Practical Guide to SOA in Healthcare
How To Succeed With Social Media
Moving domains
Five mobile CRM strategies to win the new consumer
CFO is King in 2009: Talking BPM With Appian
HP's Kelly Emo: SOA and Web 2.0 Takes IT from 'Zeroes to Heroes'
IDC Sees Rising Importance of Corporate Governance in 2009
Hype-Inflation and the Web
Strategic and Executive Control
Business Rules to Programmers: Methink thou doest protest too much I
SOA is dead! Long live SOA!
The Answer to Pervasive Business Intelligence...the Government
New Congressional Report: A Call to Action for ERM Regulation
When Not To Think About Continuous Process Improvement?
BBC Buys into Sun Spin on Open Source Software
Automating account reconciliation to deliver the double whammy: reduce costs and improve governance
Where to Find the Latest SaaS News and Breakthroughs
Titanic Compliance
Evolution of principles of Service Orientation: Service Statelessness, part 6
IT Governance: A True Confession
Sun Releases Enterprise Open Source Platform
'Back Door SOA' -- More on the SOA-Cloud Connection
SOA Visionaries with Michael Stamback, Oracle
Cloud computing, SaaS and SOA - the universal service network
No Certainties on Cloud Confidentiality
Understanding Web 2.0 Attacks
Heartland Data Breach a Failure of PCI: Mike Rothman Explains

Ronan Bradley's blog on infrastructure technology news and trends in the retail banking, captial markets and beyond.

Ronan Bradley

Ronan Bradley has specialized in business integration technologies and their application for over 15 years, View more

Recently Commented On

Monthly Archives

ADVERTISEMENT