DISTRIBUTED
DATABASES
Erika Jean F. Acibar
TOPICS:
• Centralized Databases
• Distributed Databases
• Advantaged and Disadvantages
• Replication and Data Partitioning
• Distributed Databases Architectures
• Challenges in Distributed Databases
WHAT IS A CENTRALIZED DATABASES?
• Data is stored, located and maintained at a single location only.
• Mainly used by institutions and organizations.
ADVANTAGES:
• Simple design and management
• Easy to maintain data consistency
• Lower initial cost
DISADVANTAGES:
• Single point of failure
• Limited scalability
• Performance bottlenecks
CENTRALIZED DATABASES
WHAT IS A DISTRIBUTED DATABASE?
• A database in which data is stored across multiple physical locations
• Locations may be on different servers, computers, or geographic sites
• Appears as a single database to users
ADVANTAGES:
• High availability and fault tolerance
• Better performance through parallel processing
• Easily scalable
DISADVANTAGES:
• Complex design and management
• Higher cost
• Data consistency challenges
DISTRIBUTED DATABASES
CENTRALIZED VS DISTRIBUTED DATABASES
Aspect Centralized Distributed
Location Single site Multiple sites
Availability Low High
Scalability Limited High
Fault Tolerance Low High
Complexity Low High
WHAT IS REPLICATION?
• The process of copying the same data to multiple nodes
TYPES OF REPLICATION:
• FULL REPLICATION: Entire database copied to all sites
• PARTIAL REPLICATION: Only selected data is copied
BENEFITS:
• Improves availability
• Enhance read performance
• Provides fault tolerance
WHAT IS DATA PARTITIONING?
• Dividing a database into smaller parts (fragments)
BENEFITS:
• Performance improvement
• Scalability
• Efficient Resource Utilization
• Enhance Manageability
TYPES OF PARTITIONING:
• Horizontal: Divides data by rows
• Vertical: Only selected data is copied
• Hybrid: Combination of horizontal and vertical partitioning
REPLICATION VS PARTITIONING
Feature Replication Partitioning
Data Copy Multiple Copies Single Copy
Main Goal Availability Performance
Storage Cost High Lower
Use Case Ready-heavy systems Large datasets
DISTRIBUTED DATABASE ARCHITECTURES
• Homogeneous Database: All different sites stores database identically.
FEATURES:
• Unified query language and interface
• Low integration complexity
• Efficient synchronization
DISTRIBUTED DATABASE ARCHITECTURES
• Heterogeneous Database: Different sites may use different DBMS, schemas, or data models,
making query processing and transactions difficult.
FEATURES:
• Supports interoperability between diverse systems.
• Complex query optimization and transaction management.
• Useful in mergers or collaborations between organizations.
DISTRIBUTED DATABASE ARCHITECTURES
• Client-Server Distributed Database System: the server stores and manages the databases,
while clients send queries over the network
FEATURES:
• Simplifies resource management
• Central servers can be optimized for performance
• Easily scalable with more clients
DISTRIBUTED DATABASE ARCHITECTURES
• Peer-to-Peer Distributed Database System: All nodes are equal, with no fixed client or server
roles. Each node can store data and also process queries, leading to decentralized control.
FEATURES:
• No single point of failure
• Useful in decentralized and distributed apps
• High availability and data redundancy
DISTRIBUTED DATABASE ARCHITECTURES
• Cloud-Based Distributed Database System: These systems are deployed on cloud platforms
and span multiple geographic religions for scalability and reliability.
FEATURES:
• Automatic scaling and replication
• Pay-as-you-use pricing
• Global availability and disaster recovery
CHALLENGES IN DISTRIBUTED DATABASES
• Data consistency
• Network latency
• Security concerns
• Complexity in design
THANK YOU!