We have already taken
care of this data impedance by building adapters. But, what if on one fine morning,
the C++ application starts spitting float instead of int? The existing adapter is
going to fail, and we need to rework on the adapter in this channel.
The good news is, within an organization this can be controlled and managed
since we have access to both the ends of the adapter. The scenario worsens when
the interface changes in a B2B scenario where systems between two separate
organizations interact. As we know already, this is going to happen. So, we have to
build agile interfaces.
New Systems Introducing Data Redundancy
Adding new systems is an after effect of business expansion, but there are multiple
risks associated with it. First, we need to integrate new systems with the existing
systems. Secondly, many a time, new systems introduce data redundancy. This
is because the same data might get entered into the network through multiple
interfaces. Similar is the problem of the same data duplicated at different parts of
the organization. This contradicts the requirements of Straight-Through Processing
(STP).
Pages:
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54