Reading “MDM and SOA, a Strong Partnership” on the Hub Solution Designs blog reminded me that it was about time I rescued this post from the depths of my collection of drafts.
To be useful, services must at some point deal with information, whether that’s product information, account information, a customer record or something else that is of interest to your business. It doesn’t take too long when you look at even the most basic web service examples before you spot something like ‘getCustomer’. You don’t need to look far; this post about RESTful services has account as well as customer for example.
Of course, if you aren’t writing this web service for a brand new company, the obvious question is where is the information about the customer going to come from? If you don’t consider master data management before taking the plunge with SOA, you’ll either end up with defacto master data appearing in an add hoc way, possibly based on the order services are exposed without any thought about data quality, or a whole bunch of conflicting data from duplicated services. It’s not a one way street either, master data management systems are easier with service oriented approaches.
Here’s what a few others have to say on the subject:
- SOA and MDM: Two Integration Solutions That Go Great Together?
- Master Data Management and Service-Oriented Architecture
- Master Data Management Paves the Way for SOA
Update: I read New trends in Enterprise Software Enterprise 2.0 and MDM today which also has quite a nice introduction to how MDM and SOA are related. (14 April 2009)
Notes from a small field 