Loading content
Fallback strategies define alternative behaviors when primary functions fail, reducing downtime and preserving usability. They include patterns such as graceful degradation, circuit breakers, and default responses and are applied at architectural and implementation levels to increase system reliability and recovery capabilities.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Fallback strategies define how a system switches to safe alternative behavior when primary functions fail, so core service, availability, and usability are preserved.
The term belongs to reliability and resilience practice in software and distributed systems architecture. It emerged from the problem of keeping a service useful when components, dependencies, or networks fail. Designers therefore define alternate response paths, reduced operating modes, and explicit switch rules instead of letting failures cascade unchecked.
Think of a fallback strategy as a layered safety net. The normal path runs first. If it becomes unstable or fails, a defined rule switches to a reserve path, reduces functionality, or returns a safe default response. That keeps the essential service available while noncritical parts step back and the root cause is handled later.
A second resource or route can take over when the primary one fails.
The system stays usable, but with reduced quality or scope.
Further calls to an unstable service are temporarily stopped.
A safe fallback value or simplified answer fills missing results.
Workload shifts to a backup component or backup service.
This knowledge helps when APIs, model services, databases, or other dependencies fail, slow down, or return unreliable results. Good fallback design requires prior decisions about which functions are essential, what may be reduced, and how partial failure stays visible. The trade-off is more paths, more tests, and the risk of hiding problems if monitoring is weak.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.