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

Institutions

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
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
article

Centralized vs. Decentralized Databases: A Technical Synthesis

Devanshi, Kanika Malik, Harshkant, Himanshu
Zenodo (CERN European Organization for Nuclear Research)
Distributed systems and fault tolerance
article

Centralized vs. Decentralized Databases: A Technical Synthesis

Devanshi, Kanika Malik, Harshkant, Himanshu
article en

Abstract

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.

Zenodo (CERN European Organization for Nuclear Research)
Shree Guru Gobind Singh Tricentenary University (IN)
Distributed systems and fault tolerance
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon
Centralized vs. Decentralized Databases: A Technical Synthesis — Devanshi, Kanika Malik, et al. · Zenodo (CERN European Organization for Nuclear Research) (2026) | TGRS Research Map | TGRS