Centralized vs. Decentralized Databases: A Technical Synthesis
A Database Management System (DBMS) can run on a single site under one administrative authority (centralized), or it can be spread across multiple sites with data partitioned, replicated, and sometimes controlled by independent parties (decentralized). This choice affects consistency, availability, latency, scalability, security, cost, and governance. This report is a literature-based synthesis. It defines the terminology, explains the mechanisms behind each approach (fragmentation, replication, distributed transactions, consensus, and consistency models), connects them to application settings, and examines the trade-offs. It also proposes a layered decision framework for selecting an architecture. The report finds that neither approach is universally superior. Centralized systems offer simplicity, strong consistency, and unified control, but they are limited by a single point of failure and the capacity of one site. Decentralized systems offer scale, fault tolerance, and locality, but at the price of coordination overhead, weaker or costlier consistency, and a harder governance problem. Limitations and future directions are stated explicitly. No experimental measurements are reported.
Authors
- Devanshi
- Kanika Malik
- Harshkant
- Himanshu
Institutions
- Shree Guru Gobind Singh Tricentenary University (IN)
Publication Details
- Journal
- Zenodo (CERN European Organization for Nuclear Research)
- Published
- 2026-11-21
- DOI
- https://doi.org/10.5281/zenodo.24412771
- Primary Topic
- Distributed systems and fault tolerance
- Type
- article
- Field-Weighted Citation Impact
- 0.00