# Control / Coordination / Centralization > Every term in this category is listed as one record, with its kind, its definition and its aliases, the principles whose relations name it, the principle or… Page: Ontology · Lexicon Canonical: https://banes-lab.com/ontology/lexicon#lexicon-category-control-coordination-centralization Listed in [Ontology · Lexicon](https://banes-lab.com/api/pages/ontology/lexicon.md), after [Contracts / Interfaces / Compatibility](https://banes-lab.com/ontology/lexicon/lexicon-category-contracts-interfaces-compatibility.md) and before [Coordination Surfaces](https://banes-lab.com/ontology/lexicon/lexicon-category-coordination-surfaces.md). Every term in this category is listed as one record, with its kind, its definition and its aliases, the principles whose relations name it, the principle or contract that carries the same name where one exists, and the layer its category belongs to. A tag category also gives each term an example, which is the file the tag places or the rename from a refused word onto a covering tag. ### Agreed Single Value Across Nodes - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability for distributed nodes to agree on a single value despite failures. Referenced by [Consensus](https://banes-lab.com/records/architecture/consensus.md) How it is checked Checked by [Consensus](https://banes-lab.com/records/architecture/consensus.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Automatic Failover of Leadership - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to automatically elect a new leader when the current one fails. Referenced by [Leader Election](https://banes-lab.com/records/architecture/leader-election.md) How it is checked Checked by [Leader Election](https://banes-lab.com/records/architecture/leader-election.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Central Dependency Risk - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The degree to which centralizing configuration makes the whole system depend on one config source. Referenced by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) How it is checked Checked by the tension resolution with centralized-configuration Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Central Orchestrator Bottleneck - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Routing every interaction through one central orchestrator that becomes a bottleneck and single point of failure. Referenced by [Choreography](https://banes-lab.com/records/architecture/choreography.md) How it is checked Checked by [Choreography](https://banes-lab.com/records/architecture/choreography.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Central-Orchestrator-Free Coordination - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability for services to coordinate through events without a central orchestrator. Referenced by [Choreography](https://banes-lab.com/records/architecture/choreography.md) How it is checked Checked by [Choreography](https://banes-lab.com/records/architecture/choreography.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Centralized Control - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Concentrating decision-making authority in one place so nodes cannot act independently. Referenced by [Decentralization](https://banes-lab.com/records/architecture/decentralization.md) How it is checked Checked by [Decentralization](https://banes-lab.com/records/architecture/decentralization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Centralized Control of Distributed Runtime - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to manage a distributed runtime's behavior from one central control point. Referenced by [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) How it is checked Checked by [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Centralized Coordinator Coupling - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The degree to which routing a workflow through a central coordinator couples participants to it. Referenced by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) How it is checked Checked by the tension resolution with orchestration Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Config Store - Kind: [mechanism](https://banes-lab.com/records/kind/mechanism.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition A central store that holds configuration values for many services to read. Referenced by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) How it is checked Checked by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Coordinator - Kind: [mechanism](https://banes-lab.com/records/kind/mechanism.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition A component that directs the steps of a multi-service workflow in order. Referenced by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) How it is checked Checked by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Cost/Personal Data Exposure - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The degree to which aggregating all logs centrally raises storage cost and personal-data exposure. Referenced by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) How it is checked Checked by the tension resolution with centralized-logging Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Cross-Service Analysis - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to analyze behavior across services by querying their aggregated logs. Referenced by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) How it is checked Checked by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Fully Decentralized Control - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Leaving control fully decentralized with no central plane, so global runtime policy cannot be coordinated. Referenced by [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) How it is checked Checked by [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Identity Provider - Kind: [mechanism](https://banes-lab.com/records/kind/mechanism.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition A central service that authenticates identities and issues credentials for others to trust. Referenced by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) How it is checked Checked by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Identity Provider Availability - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The degree to which every login depends on the central identity provider staying available. Referenced by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) How it is checked Checked by the tension resolution with centralized-authentication Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Independent Node Decisions - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Letting each node decide independently with no agreement, so they diverge on shared state. Referenced by [Consensus](https://banes-lab.com/records/architecture/consensus.md) How it is checked Checked by [Consensus](https://banes-lab.com/records/architecture/consensus.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Independent Ownership - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability for each node or team to own and control its part without central approval. Referenced by [Decentralization](https://banes-lab.com/records/architecture/decentralization.md) How it is checked Checked by [Decentralization](https://banes-lab.com/records/architecture/decentralization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Local-Only Logs - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Leaving logs scattered on each host with no aggregation, so cross-service analysis is impossible. Referenced by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) How it is checked Checked by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Log Aggregation - Kind: [mechanism](https://banes-lab.com/records/kind/mechanism.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition A facility that collects logs from many sources into one central store. Referenced by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) How it is checked Checked by [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Management API - Kind: [mechanism](https://banes-lab.com/records/kind/mechanism.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition A programmatic interface through which operators manage a distributed runtime's state. Referenced by [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) How it is checked Checked by [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Ordered Multi-Step Execution - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to execute the steps of a workflow in a defined order. Referenced by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) How it is checked Checked by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Pure Choreography - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Coordinating a multi-step workflow purely through choreography when central orchestration is needed, scattering its logic. Referenced by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) How it is checked Checked by [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Quorum - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The requirement that a majority of nodes agree before a decision commits. Referenced by [Consensus](https://banes-lab.com/records/architecture/consensus.md) How it is checked Checked by [Consensus](https://banes-lab.com/records/architecture/consensus.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Scattered Auth Implementations - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Reimplementing authentication separately in each service instead of centralizing it. Referenced by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) How it is checked Checked by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Scattered Configuration - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Spreading configuration across many services with no single source, so values drift out of sync. Referenced by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) How it is checked Checked by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Single-Writer Coordination - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to designate one writer for each unit of shared state, whether an elected node or the party a record names, so updates to it need no further coordination. Referenced by [Leader Election](https://banes-lab.com/records/architecture/leader-election.md), [Write Barrier](https://banes-lab.com/records/architecture/write-barrier.md) Distinct from [Automatic Failover of Leadership](https://banes-lab.com/records/lexicon/automatic-failover-of-leadership.md): Single-writer coordination makes one elected node the only writer, while leadership failover elects a new one when it fails. How it is checked Checked by [Leader Election](https://banes-lab.com/records/architecture/leader-election.md), [Write Barrier](https://banes-lab.com/records/architecture/write-barrier.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Split-Brain Coordination - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition Two nodes both believing they are leader and acting independently, corrupting shared state. Referenced by [Leader Election](https://banes-lab.com/records/architecture/leader-election.md) How it is checked Checked by [Leader Election](https://banes-lab.com/records/architecture/leader-election.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Unified Config Management - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to manage all services' configuration from one place. Referenced by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) How it is checked Checked by [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Unified Identity - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Control / Coordination / Centralization](https://banes-lab.com/ontology/lexicon/lexicon-category-control-coordination-centralization.md) - Layer: [Execution Core](https://banes-lab.com/records/layer/execution-core.md) Details Definition The ability to give users one identity recognized across all services. Referenced by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) How it is checked Checked by [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ## Links to - [capability](https://banes-lab.com/records/kind/capability.md) - [Execution Core](https://banes-lab.com/records/layer/execution-core.md) - [Consensus](https://banes-lab.com/records/architecture/consensus.md) - [Leader Election](https://banes-lab.com/records/architecture/leader-election.md) - [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - [Centralized Configuration](https://banes-lab.com/records/architecture/centralized-configuration.md) - [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - [Choreography](https://banes-lab.com/records/architecture/choreography.md) - [Decentralization](https://banes-lab.com/records/architecture/decentralization.md) - [Control Plane](https://banes-lab.com/records/architecture/control-plane.md) - [Orchestration](https://banes-lab.com/records/architecture/orchestration.md) - [mechanism](https://banes-lab.com/records/kind/mechanism.md) - [Centralized Logging](https://banes-lab.com/records/architecture/centralized-logging.md) - [Centralized Authentication](https://banes-lab.com/records/architecture/centralized-authentication.md) - [constraint](https://banes-lab.com/records/kind/constraint.md) - [Write Barrier](https://banes-lab.com/records/architecture/write-barrier.md) - [Automatic Failover of Leadership](https://banes-lab.com/records/lexicon/automatic-failover-of-leadership.md)