Adaptation describes the capability of systems and architectures to dynamically adjust behavior, configuration, or topology in response to internal state changes or external environmental conditions. The goal is to preserve robustness, availability and performance. It includes design principles, runtime control, observability and feedback loops for decision…
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 organizes, connects, or makes decisions possible.
Adaptation is the architectural principle of adjusting systems at runtime to changing conditions so availability, resilience, and performance remain stable.
In IBM's 2001 autonomic-computing initiative, a core operations problem became explicit: distributed systems were growing too complex to manage manually. Adaptation therefore names more than mere changeability. It is the deliberate readjustment of behavior, configuration, or topology through measurements, policies, and feedback loops so systems remain useful under shifting load and faults.
Think of adaptation as an operating control loop: telemetry reports load, failures, or environmental change, a policy evaluates those signals against targets, and actuators alter parameters, routing, scaling, or topology. The system then measures again. Good adaptation needs clear bounds; otherwise it can produce oscillation, side effects, or hidden coupling.
Measurements are continuously compared with targets and trigger corrections.
Metrics, logs, and signals make the current state and its causes visible.
Predefined rules decide when and how the system may respond.
The system actively changes configuration, resources, or topology instead of only reporting.
Thresholds, approvals, and hysteresis prevent frantic switching and harmful interventions.
Adaptation is useful for variable load, recurring faults, multi-region operation, autoscaling, failover, or configurable platforms. Its value depends on clearly defined goals, signals, and intervention rights; otherwise control overhead grows, behavior becomes harder to predict, and automatic changes can amplify instability.
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.