Lesson 105 - Stamp Coupling
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: Stamp Coupling (Wikipedia): https://en.wikipedia.org/wiki/Couplin...) Fundamentals of Software Architecture: https://www.amazon.com/gp/product/149... Software Architecture Monday: https://www.developertoarchitect.com/...

Lesson 104 - Architecture Styles FAQ #1

Lesson 29 - Component Coupling

Lesson 137 - Rest vs. Messaging

Lesson 25 - Architectural Abstraction

Loose vs Tight Coupling

Ex-Google Recruiter Explains Why "Lying" Gets You Hired

Lesson 109 - BASE Transactions and Eventual Consistency

Coupling Is The Biggest Challenge In Software Engineering

MIT Just Revealed the AI Bubble's Fatal Flaw

Lesson 6 - Classifying Architecture Patterns

The French Do Not Care About Work

Keynote: After the AI Hype – What’s Real, and What’s Next - Richard Campbell - 2026

You Know This Song (but the Orchestra Doesn’t) | Jacob Collier & VSO School of Music Orchestra | TED

She Asks if I Know Coldplay and This Singer Shocks The Street

Lesson 85 - Defining Scalability and Elasticity

Judge Can’t Stop Laughing At Sovereign Citizen’s Courtroom Meltdown!!!

How to Answer ANY Question (Even If You Don't Know The Answer!)

When Stupid Cops Mess With FBI Agent

Lesson 100 - My Architecture Journey: Lessons Learned

