DBMS Topics
Distributed Database
Last Updated : 21 May, 2026
A distributed database is a collection of multiple, logically interrelated databases distributed over a computer network. The data is stored at different sites nodes/loca
What is a Distributed Database?
A distributed database is a collection of multiple, logically interrelated databases distributed over a computer network. The data is stored at different sites (nodes/locations), but the system presents it to users as a single unified database.
| Site A | Site B | Site C | ||
|---|---|---|---|---|
| Delhi | Mumbai | Chennai | ||
| [EmpTable] | [OrdTable] | [ProdTable |
Key Characteristics
1. Distribution Transparency
Users should not need to know where data is physically stored.
| Location Transparency | User queries without knowing where data is |
| Replication Transparency | User unaware of multiple copies |
| Fragmentation Transparency | User unaware of data splitting |
2. Heterogeneity
Different sites may run different DBMS software (Oracle at Site A, MySQL at Site B). A distributed DBMS must handle this.
3. Local Autonomy
Each site can still operate independently when the network is unavailable.
Advantages of Distributed Databases
| Advantage | Description |
|---|---|
| Reliability | Failure of one site doesn't bring down entire system |
| Availability | Data replicated → can serve requests even during partial failures |
| Performance | Local queries execute faster at the nearest site |
| Scalability | Add more sites as data/load grows |
| Departmental ownership | Each department controls its own data |
| Reduced communication cost | Local queries don't travel over network |
Disadvantages
| Disadvantage | Description |
|---|---|
| Complexity | Much harder to manage, tune, and debug |
| Higher cost | Network infrastructure + distributed DBMS software |
| Security risks | More attack surfaces across network |
| Concurrency control | Global transactions across sites are complex |
| Consistency challenges | CAP theorem applies — cannot guarantee all three properties |
CAP Theorem
In a distributed system, you can guarantee at most two of:
| Consistency | Every read returns the most recent write |
| Availability | Every request receives a response |
| Partition Tolerance | System continues despite network partitions |
| CA Systems | Traditional RDBMS (single node) |
| CP Systems | MongoDB (with default settings), HBase, ZooKeeper |
| AP Systems | Cassandra, CouchDB, DynamoDB |
DDBMS Architecture Models
1. Client-Server Architecture
2. Peer-to-Peer Architecture
| Node 1 | Node 2 | |
|---|---|---|
| Node 3 | ←→ | Node 4 |
3. Federated Database
Multiple autonomous databases cooperate without full integration.
Distributed Transactions
Transactions that span multiple sites require coordination:
Two-Phase Commit (2PC) Protocol
| COORDINATOR | ───────────────► | Site A |
|---|---|---|
| ◄─ VOTE YES ──── | ||
| ───────────────► | Site B | |
| ◄─ VOTE YES ──── |
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Distributed Database.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this DBMS topic.
Search Terms
dbms, database management system, database notes, sql, unit, distributed, database, distributed database
Related DBMS Topics