Protocol
Design a fallback at the interface
Interfaces are natural places to define degraded behavior.
Before you use it
- Use when
- When one dependency can fail and take the whole service or process with it.
Keep this limit in mind
- Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Specify timeout, retry, cached value, manual route or safe stop at the dependency boundary, plus the conditions where degraded operation is unacceptable.
Steps
- Name the dependency failure mode.
- Choose safe degraded behavior.
- Define timeout and recovery ownership.
- Test the fallback before needing it.
An example
If an external credit check is unavailable, the process routes to manual review rather than hanging indefinitely or silently approving.
Check your result
A dependency failure produces a known bounded state instead of an improvised reaction.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDesign a fallback at the interface
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaSeparate policy from implementation mechanism
Evidence and sources
Parnas showed that modularization outcomes depend on decomposition criteria and argued for boundaries that hide changeable design decisions to improve flexibility and comprehensibility.
This is foundational software-design reasoning; organizational adaptations require separate validation.
On the Criteria To Be Used in Decomposing Systems into Modules · Abstract and design comparison
Edition and review
Version 0.1.0
No review details are supplied for this edition.