Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:c:centralized_system [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:c:centralized_system [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Centralized System ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Centralized System concentrates primary control, processing, authoritative data, or system services within a central node or central location. | ||
| + | |||
| + | Other nodes, clients, or components communicate with the central node to obtain the services or data provided by the system. | ||
| + | |||
| + | A Centralized System commonly uses a [[private: | ||
| + | |||
| + | * A Centralized System describes the allocation of system authority, processing, state, and services | ||
| + | * A Centralized Network Topology describes the arrangement and interconnection of network nodes | ||
| + | |||
| + | The central node commonly performs functions such as: | ||
| + | |||
| + | * Processing requests | ||
| + | * Maintaining authoritative data | ||
| + | * Coordinating system behavior | ||
| + | * Enforcing access controls | ||
| + | * Recording transactions | ||
| + | * Providing shared services | ||
| + | * Managing backups and recovery | ||
| + | |||
| + | A Centralized System differs from a [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //system in which primary control, processing, authoritative state, or services are concentrated within a central node or central location// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * DIDO Reference Architecture, | ||
| + | * Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Centralized System does not require all components to reside on one physical computer. | ||
| + | |||
| + | Clients, interfaces, storage devices, and supporting services can reside on multiple computers while the system retains centralized authority or control. | ||
| + | |||
| + | A central node can create a single point of control and a single point of failure unless the architecture provides redundancy or failover. | ||
| + | |||
| + | The term does not prescribe a mainframe, database technology, cloud platform, network protocol, or deployment model. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A system uses one authoritative management server to store environment records, issue management commands, and coordinate all managed nodes. | ||
| + | |||
| + | The clients and managed nodes reside on separate computers, but the management authority remains centralized. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||