|
|
||||||||||||||||||||
| Home > SOA without MDM: GIGO 2.0? | |
| Special Report: |
|
||
The garbage in, garbage out mantra is playing out again as application developers and SOA advocates use master data management (MDM) to ensure their complex, integrated systems are working on the right information. This SOA-MDM story played out before in data warehousing, when analytical data stores were created to provide a valid view of the state of the organization. There was a lot of argument about what an order entry was, or how many fields should represent a customer location, but things were resolved and data warehousing flourished. Now the same issue is paramount in the SOA space, where business operations in the form of loosely coupled applications (and some not-so-loosely coupled applications) are integrated—sometimes on the fly. So, the hunt for good, clean, valid data is on again! With, of course, a few new twists. In this five part special report, get the facts about SOA and MDM. Part 1: SOA with MDM prevents messaging confusion Part 2: SOA and MDM: New techniques address old problems
'); // -->
a young technology, but the issues it addresses have been around for years. Whereas data definition was historically aligned with BI initiatives, the emergence of MDM with SOA has empowered architects to make trustworthy data available in realtime for multiple purposes. Part 3: Data architecture project practices with SOA and MDM Part 4: MDM brings SOA and BPM closer together Part 5: With MDM and BPEL, business users become data stewards |
|
|||||||||||||||||||||||||
| About Us | Contact Us | For Advertisers | For Business Partners | Site Index | RSS |
|
|
|
|||||||