Feedback control is a conceptual pattern from control theory that measures and adjusts system behavior via feedback to achieve setpoints or reject disturbances. It defines measurement, comparison and corrective-action loops and supports stability and robustness. It is applicable across software architecture, operations and product quality.
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.
Feedback control is a control principle in which the current state, a target value, and corrective action are linked in a feedback loop so systems remain stable or compensate for disturbances.
The concept comes from control theory and cybernetics, which studied how processes can stay stable despite changing influences. Historical precursors reach back to self-regulating mechanisms such as float valves and governors; in systems and software practice, this became the model of a closed loop of measuring, comparing, and intervening.
Think of a thermostat: a sensor measures the current value, a controller compares it with the target value, and an actuator changes the control input. The effect returns later as a new measurement. This lets the system correct deviations step by step. If the feedback is too strong, too slow, or too noisy, the system may oscillate instead of settling.
Output and observation form a circle in which the effect triggers new action.
A sensor or metric provides the system's current state.
The desired target state serves as the reference for regulation.
The control element decides how to correct based on deviation and context.
A change to resources, parameters, or behavior influences the system.
External influences push the system away from the target state.
Feedback control is useful when systems must regulate load shifts, latency, quality targets, or safety limits, for example in autoscaling, rate limiting, cache control, or SLO-based alerting. It works best with reliable measurements and adjustable interventions; delays, poor signals, or excessive gain can cause oscillation, overcorrection, and extra operational work.
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.