Data Coupling

Coupling is a parameter dependency approach used cross software or cross systems.

This approach is used when there are more than one software or system is in the picture to deliver the result.

Data Coupling is about when data elements are used, to kick-off the next step in a different system. For example, in data pipeline, we are pulling data from a hospital management system e.g., when a baby is born let’s have a data dependency like, the moment the baby is registered in system, pull its data. So, it’s a cross-system data dependency or we called Data Coupling.

The disadvantage of Data Coupling approach is, if something goes wrong in the first system, dependent systems cannot move.

Let me share another old example. Old data pipeline folks will remember this one i.e., when we used to load files from another system, we had to wait till the time whole file movement is completed. The challenge was how to make sure when to start pulling like only once file is completely copied.

The workarounds for the above challenge were.

• Copy file in a different name. Once the file is completely copied, another command can rename it and pulling job can pull the required file.
• Create a temp file after the data file is completely copied so when pulling job can see temp file, it should start pulling data files.
• Now a day, export or copy or move commands are smart. When files are in progress, there is tmp add in the naming conversion of the file. Once files are copy, the same query removes the tmp word and pulling job can recognize the data file name to pull it.

Type of Coupling

• No Direct Coupling
• Data Coupling
• Stamp Coupling
• Control Coupling
• External Coupling
• Comment Coupling
• Content Coupling