This discussion is archived
1 Reply Latest reply: Apr 28, 2010 11:30 PM by 597001 RSS

MDM and data distribution architecture

589858 Newbie
Currently Being Moderated
Hi All,
I would like to ask the experts our there as to how data should be exposed to the subscribers of the master data using the BUS architecture. There are two schools of thoughts-

1) Expose tables/ views directly to the BUS subscribers
2) Encapsulate data using procedures/ functions

There are pros and cons to both approaches from my perspective

Encapsulation Pros
1) Maintainability
2) Encapsulation
3) Security
4) Performance

Encapsulation Cons
1) Complex usage for the BUS
2) Longer time to code SPs

Direct access Pros
1) Ease of usage

Direct Access Cons
1) One view for each type of access whereas SPs can be coded with Parameters for various types of access
2) Performace unles you use materialized views which in turn causes lot more maintainenance headaches

I am trying to understand what is does the "best practice" or guidelines say. Any input would be appreciated.

  • 1. Re: MDM and data distribution architecture
    597001 Journeyer
    Currently Being Moderated
    As far as the ease and of implementation and integration of CDH is concerned, you should always prefer to go for SOA/any middleware that suits your integration environment. You can also add complex business rule transformations thorough BPEL manager.
    On the other hand, coding PL/SQL APIs are time consuming and error-prone.
    In my view we should always avoid the manual coding and leverage the feature of recent technologies as far as the budget is not a concern :-)

    Hope this helps.


  • Correct Answers - 10 points
  • Helpful Answers - 5 points