Databases Reference
In-Depth Information
12.1.4.
Consequences of integration models
The three models that we have just described can co-exist
within the same information system, at the same time for
different MDM repositories, but also for the same MDM
repository.
For example, an address repository can base itself on a
tight coupling MDM system as long as its availability
permits it, and then automatically swing to a loose coupling
MDM system in case of unavailability, in order not to block
the transactional systems.
Table 12.1 draws up a comparison between the three
integration models.
Weak
Coupling
Tight
Coupling
Loose
Coupling
Characteristics
The synchronization between
the MDM system and other
databases is done by
benefiting from the
management of the lifecycle
of data
Obligatory
Strongly
recommended
Strongly
recommended
The availability of the MDM
system
No
Yes
No
conditions
the
execution of other systems
The propagation of the MDM
update towards other
databases is done in real
time
No
Yes
No
The MDM system is used in
the production environment
Yes
Yes
No
Real-time read access to the
MDM system is possible
Yes
Yes
No
Real-time update access to
the MDM system is possible
No
Yes
Yes
The MDM system
performance problems
impact those of other systems
No
Yes
No
Table 12.1.
A summary of the MDM integration models
