Parallel Databases
Parallel Databases
Introduction
• A parallel database system seeks to improve performance through
parallelization of various operations, such as loading data, building
indexes and evaluating queries.
• Parallel databases improve processing and input/output speeds by
using multiple CPUs and disks in parallel.
• In parallel processing, many operations are performed
simultaneously, as opposed to serial processing, in which the
computational steps are performed sequentially.
ARCHITECTURES FOR
PARALLEL DATABASES
Shared memory system
• In a shared-memory system, multiple CPU·s are attached to an
interconnection network and can access one common region of main
memory
• Shared memory system have large amount of cache memory at each
processors, so referencing of the shared memory is avoided.
Shared Disk System
• In a shared-disk system, each CPU has a private memory and direct
access to all disks through an interconnection network.
• Each processor has its own memory so the data sharing is efficient.
• Advantages of Shared Disk System: Fault tolerance is achieved using
shared disk system.
Fault tolerance: If a processor or its memory fails, the other processor
can complete the task. This is called as fault tolerance.
• Disadvantage of Shared Disk System: Shared disk system has limited
scalability as large amount of data travels through the interconnection
channel. If more processors are added the existing processors are
slowed down.
Shared nothing disk system
• In a, shared-nothing system each CPU has local main memory and
disk space, but no two CPUs can access the same storage area.
• Processors can communicate with each other through
intercommunication channel.
INTRODUCTION TO
DISTRIBUTED
DATABASES
What are distributed databases?
• Distributed database is a system in which storage devices are not
connected to a common processing unit.
• Database is controlled by Distributed Database Management System
and data may be stored at the same location or spread over the
interconnected network. It is a loosely coupled system.
• Shared nothing architecture is used in distributed databases.
Goals of Distributed Database system.
• Reliability: In distributed database system, if one system fails down or
stops working for some time another system can complete the task.
• Availability: In distributed database system reliability can be achieved
even if sever fails down. Another system is available to serve the
client request.
• Performance: Performance can be achieved by distributing database
over different locations. So the databases are available to every
location which is easy to maintain.
Types of distributed databases.
• Homogeneous distributed databases system:
• Homogeneous distributed database system is a network of two or more
databases (With same type of DBMS software) which can be stored on one or
more machines.
• So, in this system data can be accessed and modified simultaneously on
several databases in the network. Homogeneous distributed system are easy
to handle.
• Heterogeneous distributed database system.
• Heterogeneous distributed database system is a network of two or more
databases with different types of DBMS software, which can be stored on one
or more machines.
• In this system data can be accessible to several databases in the network with
the help of generic connectivity (ODBC and JDBC).
Architectures of
Distributed DBMS
Client-server architecture of Distributed
system.
• A client server architecture has a number of clients and a few servers
connected in a network.
• A client sends a query to one of the servers. The earliest available
server solves it and replies.
• A Client-server architecture is simple to implement and execute.
Collaborating server architecture.
• Collaborating server architecture is designed to run a single query on
multiple servers.
• Servers break single query into multiple small queries and the result is
sent to the client.