Databases Reference
In-Depth Information
The decision surrounding the integration models is based
around three possible approaches: weak coupling, tight
coupling and loose coupling. We now describe each of them.
12.1.1.
Weak coupling
In this integration model, the MDM system is used in a
desynchronized manner. The following example shows the
behavior of weak coupling during the update of a Customer's
within a CRM (Customer Relationship Management) system.
1
Update +
commit
CRM
Other system
Other system
4
Other system
Correction
if needed
via workflow
Address
Adresse
Adresse
Address
Request: data validation
Reply: ok, error
2
3
5b
MDM
If ok then
data synchronization
5a
Address
version/ data history
Read
Figure 12.2.
Weak MDM coupling
The customer relationship management system ensures
the address management (stage 1), in an autonomous
fashion and within its own transactional scope. At the same
time, it sends the new address or the modification of an
already existing address to the MDM system, so that the
repository validates it and ensures version and history
management (stage 2). If the address is valid, then the MDM
system immediately diffuses it towards other systems that
are supposed to use the address at its most accurate value
(stage 5a) and meets the consultation needs (stage 5b). On
the other hand, if the MDM system does not validate the
address then it sends an error message to the CRM system
that must be able to correct it (stages 3 and 4) and the other
systems are not updated.
