> management rather than continuing to duplicate data into ODS and DWH
> data stores. But SOA/MDM takes a long time, and ODS/DWH is the
> accepted means to support decision support/reporting requirements
> for the interim.
I don't get the connection between master data management and an ODS
or DW. A working, maintainable ODS or DW today already requires good
master data management. This is nothing new, any organization that
does not have good master data is most likely painfully aware of the
fact.
And of course, master data management alone says nothing about the
actual business measurements and how they are used. Services executing
business transactions may need a recent or even deep history of
various business measurements to make good decisions. We can invent
new ways to do that, but we can also fall back on the best practices
of that pre-SOA era. (!) Well-defined databases have their place and
are not anathema in this brave, new world. (Just think of the US' TIA
effort.)
Duplicating data is not a bad thing in and of itself. In fact a
well-defined SOA can help manage duplication reliably. An event-push
approach can help systems evolve away from cumbersome, infrequent
ETL. But there are plenty of reasons to duplicate data across several
ODS and/or DW databases.
The idea that SOA changes everything, and "service-orient or be
doomed" is a bill of goods. "Boondoggle" is a word we used to use
back in my home town.
-Patrick
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
