Autonomic Computing¶

A computing architecture in which monitored components use policies and feedback loops to configure, heal, optimize, and protect themselves with minimal direct administration.

Version: v1 · 2026-09-28 · History
Domain-specific #: 8089
Domain group: Applied Sciences & Engineering
Origin domain: Computer Science & Software Engineering
Subdomain: Self Managing Systems → Computer Science & Software Engineering

Core Idea¶

Autonomic computing is a self-managing architecture in which monitored components use policies and feedback loops to configure, heal, optimize, and protect computing resources. Sensors, knowledge, analysis, planning, and effectors form a MAPE-K loop while human operators set goals and constraints rather than issuing every low-level action. The common MAPE or MAPE-K loop links monitoring, analysis, planning, execution, and shared knowledge. The common MAPE or MAPE-K loop links monitoring, analysis, planning, execution, and shared knowledge.

How would you explain it like I'm…

The Computer That Looks After Itself

Your body keeps you warm, heals scrapes, and breathes without you having to think about it. Autonomic computing is about making computers that look after themselves in a similar way: they notice problems and fix them on their own. But people still set the rules for what the computer is allowed to do.

Computers That Manage Themselves

Autonomic computing means designing computer systems that can take care of themselves, following big goals set by people. Instead of a person fixing every little problem, the system keeps watching itself, figures out what's going on, makes a plan, and carries it out. It can set itself up, heal itself when something breaks, tune itself to run better, and protect itself from attacks. People still decide the goals, the limits, and what matters most. The system should also explain what it did, so people can check it when things go wrong.

Policy-Driven Self-Management

Autonomic computing designs systems that manage themselves under high-level policies instead of relying on administrators for every low-level change. Components sense their own state and environment, analyze conditions, plan a response, and execute it through controlled actions — the MAPE-K loop: Monitor, Analyze, Plan, Execute, over shared Knowledge. The goals are usually described as self-configuration, self-healing, self-optimization, and self-protection, and broader accounts add self-awareness, learning, and self-explanation. Crucially, this is constrained autonomy, not freedom from human control. Operators set objectives, acceptable ranges, priorities, and safety limits, and the system must adapt transparently, coordinate with other parts, and expose enough explanation and control that failures or policy conflicts can be audited.

Autonomic computing is an approach to designing computing systems that manage themselves under high-level policies. Rather than requiring administrators to diagnose and effect every low-level change, autonomic components sense their own state and environment, analyze conditions, plan a response, and execute it via controlled effectors. The canonical architecture is the MAPE or MAPE-K loop: monitoring, analysis, planning, and execution, linked by shared knowledge. It supports self-configuration, self-healing, self-optimization, and self-protection, and broader accounts add self-awareness, learning, regulation, organization, and explanation. Self-management is constrained autonomy, not the absence of human governance: operators set objectives, acceptable ranges, priorities, and safety boundaries. Within those constraints the system must adapt transparently, coordinate with other components, anticipate demand, and expose enough explanation and control that failures and policy conflicts can be audited.

Scope of Application¶

The architecture applies where computing complexity, variability, or scale makes direct low-level administration costly and error-prone. The architecture applies to complex computing systems with observable state, controllable resources, and policy-defined objectives.

Cloud and distributed systems. Controllers allocate resources, recover services, and maintain objectives across nodes.
Infrastructure management. Components configure and repair operating, network, and database layers.
Security. Self-protection detects threats and adapts defenses within policy.
Performance. Self-optimization tunes resources against service-level requirements.
Mobile and pervasive systems. Components adapt to changing connectivity, context, and demand.

Clarity¶

Name the managed resources, sensed variables, knowledge model, policies, analysis and planning logic, effectors, and target self-* property. Show the closed loop and escalation path. A product should not be called autonomic merely because it has an automated installer, alerting system, or isolated optimizer. The closest near miss sets the boundary: Ordinary automation is the nearest near miss: it executes predefined tasks, while autonomic computing emphasizes feedback, self-awareness, adaptation, and policy-level governance.

Manages Complexity¶

Autonomic computing compresses thousands of low-level management decisions into policy-governed control loops. It makes distributed complexity tractable by localizing sensing and adaptation, but introduces higher-order problems of controller interaction, observability, stability, policy conflict, and accountability. The central autonomy–operator control tradeoff is this: Low-level independence reduces workload but can obscure or outrun human intent. A second local optimization–global stability tension matters because Independent controllers can satisfy local goals while producing oscillation or system-wide harm.

Abstract Reasoning¶

Use three linked moves: translate operator goals into measurable policies, priorities, and invariants; model resources, environment, capabilities, dependencies, and uncertainty in the knowledge base; close the monitor–analyze–plan–execute loop and test both normal adaptation and failure recovery. As a collapse test, the case exits when sensing, decision, or actuation is absent and low-level management remains external. A fourth check is to analyze interacting controllers for oscillation, conflict, and unsafe emergent behavior.

Knowledge Transfer¶

The MAPE-K structure transfers across cloud, network, security, and embedded management where sensors and effectors close a policy-guided loop. Biological autonomic-nervous-system language is inspiration, not identity. Feedback, adaptation, and governance carry broader patterns while the named architecture remains computing-specific. No canonical parent prime is currently asserted; broader structural comparisons remain related-prime analogies until separately adjudicated in the DAG. Monitoring and effectors close the management loop. Plans change system configuration as conditions vary.

Neighborhood in Abstraction Space¶

Autonomic Computing sits in a moderately populated region (48^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Software & Systems Architecture (29 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08