Databases Reference
In-Depth Information
For this integration model to work, it is imperative that
the lifecycle of the “address”
business object is modeled. The
state of the address has different values depending on its
synchronization level between the MDM and other systems:
to be validated, validated, to be completed, etc.
This is a weak coupling model as the MDM availability
does not condition the execution of other systems, at least as
long as the updates must not be propagated immediately.
12.1.2.
Tight coupling
In this integration model, the MDM system is
synchronized in real time with the other systems.
Applied to the management of the address, Figure 12.3
shows the synchronization that should be implemented.
1
Update
request
CRM
Other system
Other system
4
Other system
Address
Adresse
Update
commit
Adresse
Address
synchronized
Request: data update
Reply: ok, error
2
3
5b
MDM
If ok then
data synchronization
5a
Address
version/ data history
Read
Figure 12.3.
Tight coupling MDM
In this scenario, the CRM is not autonomous. It cannot
manage the addresses without being synchronized
beforehand with the MDM system; the MDM system is then
a single point of failure. In other words, if the MDM system
is not available, the CRM can no longer manage addresses.
