Dead End
This anti-pattern is about not isolating risky components like external vendor's unavailability etc for critical execution. Hence, the name "dead end" is coined because you're at it, without alternatives.
Consequences
Consequences
- Downtime due to vendor or commercial off-the-shelf (COTS) unavailability.
Symptoms
Symptoms
- No isolation with vendor or volatile feature.
Causes
Causes
- No isolation with vendor or COTS interface.
- Using volatile interface in reusable software.
Fixing Recipes
Fixing Recipes
- Re-plan resources for vendor lock-in.
- Refactor to isolate volatile interfaces.
- Remove codes when necessary.
- Re-negotiate and have risk mitigation scenario tested (e.g. missing vendor, lost of data-center, etc.)