0% found this document useful (0 votes)
13 views13 pages

Distributed Design Strategies

This document discusses various strategies for designing distributed database systems, including data replication techniques like transactional, snapshot and merge replication, and data fragmentation approaches like vertical, horizontal and hybrid fragmentation. It provides details on each strategy and examples of their applications.

Uploaded by

Samip Sen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views13 pages

Distributed Design Strategies

This document discusses various strategies for designing distributed database systems, including data replication techniques like transactional, snapshot and merge replication, and data fragmentation approaches like vertical, horizontal and hybrid fragmentation. It provides details on each strategy and examples of their applications.

Uploaded by

Samip Sen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Distributed Design Strategies

Name – Samip Sen


Class roll no. - 69
MAKAUT roll no. - 12200121010
Department - CSE
Subject with code - Distributed Database Management System (PEC-IT601B)
St. Thomas’ College of Engineering & Technology
Date of Submission –26-01-2024
Contents
Introduction................................................................3
Different Strategies....................................................4
Data Replication.........................................................5
Transactional Replication..........................................6
Snapshot Replication.................................................7
Merge Replication......................................................7
Replication Schemes..................................................8-9
Fragmentation............................................................9
Vertical Fragmentation.............................................10
Horizontal Fragmentation.......................................10
Hybrid Fragmentation..............................................11
Application.................................................................12
Introduction

• A distributed database is basically a database that is not limited to one system, it is


spread over different sites, i.e, on multiple computers or over a network of computers.A
distributed database system is located on various sites that don’t share physical
components.
• There are strategies that aid in adopting the designs.The strategies can be broadly
divided into replication and fragmentation. However, in most cases, a combination of the
two is used.
Different Strategies
Data Replication -
1. Transactional Replication
2. Snapshot Replication
3. Merge Replication
Data Replication Schemes -
Full Replication,
Partial Replication,
No Replication
Fragmentation – 1.Vertical Fragmentation
2. Horizontal Fragmentation
3. Hybrid Fragmentation
Data Replication
• Data replication is a process of making the multiple copies of database available on servers.
• Replication is done in such a way so that the data is always same on all sites and synchronized
whenever there is a change.
• This distributed database approach provides better performance and availability. It also helps
to recover data in case of a server failure.

Types of Data Replication


There are three types of data replication approaches in DBMS:
1.Transactional replication
2. Snapshot replication
3. Merge replication
Transactional Replication
• The transactional replication works on a concept of publisher and subscriber.
• Publisher:The primary database that publishes data to all the secondary databases called
subscribers.
• Subscriber:These are the secondary databases, these are nothing but the copies of the primary
database.These subscriber receives updates from the publisher as and when there is a change in
the publisher database.
Snapshot Replication Merge Replication
• In this approach, the snapshot of publisher • The further changes made to the publisher
database is taken at a specific moment of database are made available to the
time and that snapshot is shared with all subscribers using triggers
the subscribers. • Merge replication allows publishers and
• Snapshot replication is slower than subscribers to make changes in the database
transactional replication, as the changes are and these changes are replicated to other
not pushed real-time rather they are publisher and subscribers.
pushed after a specific interval.
Replication Schemes • Partial replication: In partial
• Full replication: In full replication, only the data that is frequently
replication, the entire database is accessed is replicated on every site of
available at every site of the distributed database.
distributed database.
• No replication Fragmentation
• No replication means, each fragment is stored • The process of dividing the database into a
exactly at one site. smaller multiple parts is called
as fragmentation.
• These fragments may be stored at different
locations.
• The data fragmentation process should be
carried out in such a way that the
reconstruction of original database from the
fragments is possible.
Horizontal Fragmentation Vertical Fragmentation
• It divides a table horizontally into a group of • It divides a table vertically into a group of
rows to create multiple fragments or columns to create multiple fragments or
subsets of a table. subsets of a table.
• These fragments can then be assigned to • These fragments can then be assigned to
different sites in the database. different sites in the database. Reconstruction
Reconstruction is done using UNION or is done using full outer join operation.
JOIN operations.
Mixed or Hybrid Fragmentation
• It is done by performing both horizontal and
vertical partitioning together. It is a group of
rows and columns in relation.
Application
• The strategies for designing distributed databases have various applications across different
domains, and the choice of strategy depends on the specific requirements and constraints of each
application.
• Fault Tolerance:
• Application: Cloud computing platforms, distributed storage systems, and critical infrastructure.
• Use Case: Detecting and recovering from node failures to ensure continuous operation and data
availability.
• Data Locality:
• Application: Geographically distributed applications, edge computing, and systems with latency-
sensitive workloads.
• Use Case: Collocating data and computation to reduce communication latency and improve
overall system performance.
Thank You.

You might also like