# The lex records whose category is control-coordination-centralization

This index as JSON: https://banes-lab.com/json/api/facets/lex/category/control-coordination-centralization

## Entries

- [Central Orchestrator Bottleneck](https://banes-lab.com/records/lex/central-orchestrator-bottleneck.md): Routing every interaction through one central orchestrator that becomes a bottleneck and single point of failure.
- [Centralized Control](https://banes-lab.com/records/lex/centralized-control.md): Concentrating decision-making authority in one place so nodes cannot act independently.
- [Fully Decentralized Control](https://banes-lab.com/records/lex/fully-decentralized-control.md): Leaving control fully decentralized with no central plane, so global runtime policy cannot be coordinated.
- [Independent Node Decisions](https://banes-lab.com/records/lex/independent-node-decisions.md): Letting each node decide independently with no agreement, so they diverge on shared state.
- [Local-Only Logs](https://banes-lab.com/records/lex/local-only-logs.md): Leaving logs scattered on each host with no aggregation, so cross-service analysis is impossible.
- [Pure Choreography](https://banes-lab.com/records/lex/pure-choreography.md): Coordinating a multi-step workflow purely through choreography when central orchestration is needed, scattering its logic.
- [Scattered Auth Implementations](https://banes-lab.com/records/lex/scattered-auth-implementations.md): Reimplementing authentication separately in each service instead of centralizing it.
- [Scattered Configuration](https://banes-lab.com/records/lex/scattered-configuration.md): Spreading configuration across many services with no single source, so values drift out of sync.
- [Split-Brain Coordination](https://banes-lab.com/records/lex/split-brain-coordination.md): Two nodes both believing they are leader and acting independently, corrupting shared state.
- [Agreed Single Value Across Nodes](https://banes-lab.com/records/lex/agreed-single-value-across-nodes.md): The ability for distributed nodes to agree on a single value despite failures.
- [Automatic Failover of Leadership](https://banes-lab.com/records/lex/automatic-failover-of-leadership.md): The ability to automatically elect a new leader when the current one fails.
- [Central-Orchestrator-Free Coordination](https://banes-lab.com/records/lex/central-orchestrator-free-coordination.md): The ability for services to coordinate through events without a central orchestrator.
- [Centralized Control of Distributed Runtime](https://banes-lab.com/records/lex/centralized-control-of-distributed-runtime.md): The ability to manage a distributed runtime's behavior from one central control point.
- [Cross-Service Analysis](https://banes-lab.com/records/lex/cross-service-analysis.md): The ability to analyze behavior across services by querying their aggregated logs.
- [Independent Ownership](https://banes-lab.com/records/lex/independent-ownership.md): The ability for each node or team to own and control its part without central approval.
- [Ordered Multi-Step Execution](https://banes-lab.com/records/lex/ordered-multi-step-execution.md): The ability to execute the steps of a workflow in a defined order.
- [Single-Writer Coordination](https://banes-lab.com/records/lex/single-writer-coordination.md): The ability to designate one elected node as the sole writer to coordinate updates.
- [Unified Config Management](https://banes-lab.com/records/lex/unified-config-management.md): The ability to manage all services' configuration from one place.
- [Unified Identity](https://banes-lab.com/records/lex/unified-identity.md): The ability to give users one identity recognized across all services.
- [Config Store](https://banes-lab.com/records/lex/config-store.md): A central store that holds configuration values for many services to read.
- [Coordinator](https://banes-lab.com/records/lex/coordinator.md): A component that directs the steps of a multi-service workflow in order.
- [Identity Provider](https://banes-lab.com/records/lex/identity-provider.md): A central service that authenticates identities and issues credentials for others to trust.
- [Log Aggregation](https://banes-lab.com/records/lex/log-aggregation.md): A facility that collects logs from many sources into one central store.
- [Management API](https://banes-lab.com/records/lex/management-api.md): A programmatic interface through which operators manage a distributed runtime's state.
- [Quorum](https://banes-lab.com/records/lex/quorum.md): The requirement that a majority of nodes agree before a decision commits.
- [Central Dependency Risk](https://banes-lab.com/records/lex/central-dependency-risk.md): The degree to which centralizing configuration makes the whole system depend on one config source.
- [Centralized Coordinator Coupling](https://banes-lab.com/records/lex/centralized-coordinator-coupling.md): The degree to which routing a workflow through a central coordinator couples participants to it.
- [Cost/Personal Data Exposure](https://banes-lab.com/records/lex/cost-personal-data-exposure.md): The degree to which aggregating all logs centrally raises storage cost and personal-data exposure.
- [Identity Provider Availability](https://banes-lab.com/records/lex/identity-provider-availability.md): The degree to which every login depends on the central identity provider staying available.