Scribd
Upload
20 views

Advance DBMS

The document discusses several architectures for parallel and distributed databases. It describes shared-nothing, shared-disk, shared-memory, massively parallel processing (MPP), and hybrid architectures for parallel databases. For distributed databases, it covers homogeneous, heterogeneous, client-server, replicated, and federated architectures. It also provides overviews of discretionary access control (DAC) and the Department of Defense (DOD) security levels, as well as an overview of the PostgreSQL open-source database system and its key features.

Uploaded by

Purva Sukhwal
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
20 views

Advance DBMS

The document discusses several architectures for parallel and distributed databases. It describes shared-nothing, shared-disk, shared-memory, massively parallel processing (MPP), and hybrid architectures for parallel databases. For distributed databases, it covers homogeneous, heterogeneous, client-server, replicated, and federated architectures. It also provides overviews of discretionary access control (DAC) and the Department of Defense (DOD) security levels, as well as an overview of the PostgreSQL open-source database system and its key features.

Uploaded by

Purva Sukhwal
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

ADVANCE DBMS

1. Architectures for parallel databases:


Parallel databases are designed to handle large volumes of data by distributing the workload
across multiple processors or nodes. This parallel processing enables faster query execution
and better scalability.

There are several architectures for parallel databases, and they can be broadly categorized
into the following types:

Shared-Nothing Architecture:

 In this architecture, each processor or node has its own dedicated memory and storage.
 Data is partitioned across nodes, and each node independently processes its subset of
data. Communication between nodes is required for queries that involve multiple
partitions.

Shared-Disk Architecture:

 In this architecture, multiple nodes share access to a common storage system.


 Each node has its own processor and memory but can access data stored on a shared disk.

Shared-Memory Architecture:

 In this architecture, multiple processors share access to a centralized, shared memory.


 All processors can directly access any part of the data, eliminating the need for data
partitioning.

Massively Parallel Processing (MPP) Architecture:

 MPP systems combine the principles of shared-nothing and shared-disk architectures.


 Data is distributed across multiple nodes, each with its own processor and memory.

Hybrid Architectures:

 Some databases combine elements of multiple architectures to achieve a balance between


performance and flexibility.
 For example, a system might use a shared-nothing approach for certain types of queries
and a shared-disk approach for others.
2. Distributed DBMS Architectures:
Distributed Database Management Systems (DDBMS) are designed to store and manage
data across multiple nodes or sites in a network. These systems provide advantages such as
improved scalability, fault tolerance, and better performance.

Here are some common distributed DBMS architectures:

Homogeneous Distributed Database Architecture:


All sites use the same DBMS.

 Offers a unified view of the distributed database.


 Provides seamless integration and consistency across distributed nodes.

Heterogeneous Distributed Database Architecture:

 Different DBMS products are used at different sites.


 Requires middleware or gateway systems for communication and data exchange.
 Enables integration of diverse systems in a distributed environment.

Client-Server Architecture:

 Clients interact with a central server.


 The server manages the database, while clients access and manipulate data through
requests.
 Common in scenarios with a centralized database server and multiple client applications.

Replicated Database Architecture:

 Copies of the same database are maintained on multiple nodes.


 Changes to data in one location are propagated to ensure consistency.
 Enhances fault tolerance and improves performance through data redundancy.

Federated Database Architecture:

 Integrates multiple autonomous databases into a single logical view.


 Each database retains autonomy, managed by a federated database management system.
 Enables distributed data access without the need for global schema integration.
3. Discretionary Access Control:
Here's a brief overview of Discretionary Access Control (DAC) in 5 points:

User-Based Access Control:

 DAC is a security model that grants or restricts access to resources based on the
discretion of the resource owner or administrator.
 Access permissions are assigned to individual users or groups at the discretion of the data
owner.

Access Permissions:

 Users have discretion over who can access their resources and what level of access is
granted.
 Access permissions typically include read, write, execute, and delete privileges, among
others.

Access Control Lists (ACLs):

 DAC is often implemented through Access Control Lists (ACLs) associated with each
resource.
 ACLs list the users or groups allowed access and the specific actions they are permitted to
perform.

Resource Owner Authority:

 The resource owner (or administrator) has the authority to modify access permissions for
their resources.
 This allows for flexibility in managing access based on changing requirements or security
considerations.

Granular Control:

 DAC provides granular control over access at the level of individual files, folders, or
other resources.
 This fine-grained control allows for customization of access rights to meet the specific
needs of different users or groups.
4. DOD Security Levels:
The Department of Defense (DOD) uses a system of security levels to classify information
and protect it according to its sensitivity.

The DOD security levels are part of the Information Assurance Workforce Improvement
Program (8570.01-M) and are classified into three levels:

a) Unclassified:

This level includes information that does not require protection against unauthorized
disclosure.

Although it is not classified, unclassified information may still have certain handling and
dissemination restrictions.

b) Classified:

Classified information is further divided into three levels based on sensitivity: Confidential,
Secret, and Top Secret.

The classification is determined by the potential damage to national security if the


information is disclosed.

Individuals with the appropriate security clearance are granted access to classified
information based on the level of classification.

Confidential: Information that could reasonably be expected to cause damage to national


security if disclosed to unauthorized sources.

Secret: Information that could cause serious damage to national security if disclosed.

Top Secret: Information that could cause exceptionally grave damage to national security if
disclosed.

c) Special Access Programs (SAP):

This is an additional level that involves highly classified information beyond Top Secret.

Access to SAP information is restricted to individuals with a specific need-to-know, and even
those with a Top Secret clearance may not automatically have access.
5. POSTGRES:
PostgreSQL is a powerful, open-source relational database management system (RDBMS)
known for its advanced features, extensibility, and compliance with SQL standards.

Here are key points about PostgreSQL:

 Open-Source Nature: PostgreSQL is released under the PostgreSQL License, a


permissive open-source license that allows users to use, modify, and distribute the
software freely.
 Relational Database Management System (RDBMS): As an RDBMS, PostgreSQL
stores data in tables and supports complex queries, transactions, and relationships
between tables.
 Standards Compliance: PostgreSQL adheres to SQL standards and supports a wide
range of data types, indexing mechanisms, and advanced features like full-text search,
JSON, and XML.
 Extensibility and Customization: Users can define their own data types, operators, and
functions, making PostgreSQL highly extensible. The system supports stored procedures,
triggers, and other customizations to meet specific application needs.
 Concurrency and ACID Compliance: PostgreSQL supports concurrent access by
multiple users and ensures the Atomicity, Consistency, Isolation, and Durability (ACID)
properties of transactions.
 Community Support: PostgreSQL has a large and active community of developers and
users who contribute to its development and provide support through forums and mailing
lists.
 Scalability: PostgreSQL is designed to scale from small applications to large, enterprise-
level systems. It supports both horizontal and vertical scaling approaches to accommodate
varying workloads.
 Security Features: Provides robust security features, including SSL support, data
encryption, and user authentication and authorization mechanisms.
 Popular Tools: Various tools complement PostgreSQL, such as pgAdmin for database
administration, and extensions like PostGIS for geospatial data.
 Use Cases: PostgreSQL is used in a wide range of applications, including web
development, data warehousing, geographic information systems (GIS), and more.

You might also like