Coupling is a relationship in which one software element can influence another. Loose coupling limits that influence; tight coupling makes it significant. section 4.1
Four forms of coupling affect development or runtime behavior:
- Design-time: a change to one element may require changing another. section 4.1.1
- Build-time: changing one element requires another to be recompiled and retested. section 4.1.1
- Runtime: one element’s failure causes another to fail. section 4.1.1
- Infrastructure: elements share resources, such as a database, and one element’s behavior affects the other. section 4.1.1
Minimize coupling to support team autonomy, faster deployment, availability, and lower latency. Some coupling is inevitable, and eliminating it can have significant drawbacks. section 4.6
Figure 4.1 There are four different types of coupling: design-time, build-time, runtime, and infrastructure
Use the figure to compare the four forms of coupling. section 4.1.1





















