Software Architecture Patterns, Antipatterns, and Pitfalls
by Mark Richards, Neal Ford, Raju Gandhi
Chapter 16. Stamp Coupling Antipattern
When services communicate with one another they must agree on what kind of data to pass back and forth between them—in other words, their contract. A contract specifies what attributes (data) are sent to message consumers, and in some cases the data types for each attribute. This chapter describes how certain practices in creating contracts between services or systems can lead to the Stamp Coupling antipattern.
Because this chapter is dealing with an antipattern, the “Improved” and “Degraded” metadata categories in Table 16-1 refer to the characteristics that are correspondingly improved and degraded when adopting this antipattern.
| CATEGORY | METADATA |
|---|---|
CONTEXT: |
Contracts, Event-Driven Architecture, Message-Based Architectures, Microservices |
IMPROVED: |
Adaptability, Elasticity, Evolvability, Simplicity |
DEGRADED: |
Bandwidth Usage |
How Specific Should My Contract Be?
Architects are faced with ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access