According to wikipedia, “Stamp coupling occurs when modules share a composite data structure and use only parts of it, possibly different parts (e.g., passing a whole record to a function that needs only one field of it).” Is this significant? Should you worry about stamp coupling? How does it impact architecture? In this lesson Mark Richards illustrates how stamp coupling happens and discusses two reasons why this form of coupling is so bad, particularly within a microservices architecture. He then goes on to identify various techniques for avoiding stamp coupling and the associated bandwidth issues that go along with this form of coupling.
Reference Links:
Software Architecture Monday: https://bit.ly/3dadEe3
Fundamentals of Software Architecture: https://amzn.to/3rgFLjY
Software Architecture: The Hard Parts: https://amzn.to/3BjMMF2
Training Classes: https://www.developertoarchitect.com/training/