Scribd
Upload
6 views

Assignment#1

Uploaded by

53180
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

Assignment#1

Uploaded by

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

TYPES OF DBMS

Assignment #1

Database Systems

SUBMITTED BY:
HAFIZ MUHAMMAD SAAD

SAP ID:
53180

SUBMITTED TO:
MS. TUBA MANSOOR

DEPARTMENT OF COMPUTER SCIENCE

RIPHAH INTERNATIONAL UNIVERSITY


Hafiz Muhammad Saad BSSE-3B Sap ID: 53180

Question: Compare and contrast the types of Database Management Systems (DBMS),
discussing their structures, key features, advantages, and disadvantages. Where we use
such database. Real-life example.
Types of Database Management System (DBMS)
➢ Relational DBMS (RDBMS)
➢ Hierarchical DBMS
➢ Object Oriented DBMS (OODBMS)
➢ NoSQL DBMS
➢ Centralized DBMS
➢ Distributed DBMS
➢ Cloud DBMS
➢ Network DBMS

Relational DBMS (RDBMS)


Data Structure: The data are stored in tables in rows and columns. RDBMS uses SQL structured query
language to interact with the data. [1]
Example: MySQL, PostgreSQL, Oracle.
Use Cases: Transactional systems such as banking, ERP, and customer relationship management (CRM)
systems.

Hierarchical DBMS
Data Structure: Organizes data in a tree-like structure, where each record has a single parent.
Example: IBM's Information Management System, or IMS.
Use Cases: Legacy systems, especially in banking and telecommunications where data needs to be accessed
quickly.

Object Oriented DBMS (OODBMS)


Data Structure: It holds data as objects, incorporating object-oriented principles.
Example: db4o, ObjectDB.
Use Cases: Applications that need to store and manage complex data, like computer-aided design (CAD) or
multimedia applications.

NoSQL DBMS
Data Structure: Non-relational, which might be in key-value stores, document-based, wide-column stores,
or graph databases.
Example: MongoDB (document-based), Redis (key-value), Cassandra (wide-column), Neo4j (graph-based).
Use Cases: Real-time applications, big data, systems with a dynamic structure of data such as social networks
and content management systems.

Centralized DBMS
Data Structure: In the centralized DBMS, all data is stored, processed, and managed within a single server,
and users obtain data from a remote location over the network. It provides centralized control over data management.
Example: Airline Reservation Systems, Early Banking Systems, University Administration
Use Cases: Central control over vital information such as census records.
Distributed DBMS
Data Structure: A Distributed DBMS manages a database that is spread out over more than one place or
node. Each node stocks part of the data, and the system lets the users access and manipulate the data as if it were all in
a single database.
Example: Google Cloud, Amazon DynamoDB.
Use Cases: E-commerce Platforms, Social Media Applications, Telecommunications.

Riphah International University


Hafiz Muhammad Saad BSSE-3B Sap ID: 53180

Cloud DBMS
Data Structure: A Cloud DBMS refers to a database management system hosted on cloud infrastructure
allowing users the opportunity to access, manage, and store information over the internet. It can be provided as a service
(DBaaS) and usually supports different types of databases such as relational, NoSQL, and in-memory.
Example: Microsoft Azure, Google Cloud Firestore.
Use Cases: Web and mobile applications, Backup and Recovery.
Network DBMS
Data Structure: A network DBMS is a database management system represented through a network model
that takes the shape of nodes and links, thus much more complex than that of the hierarchical model.
Example: IDMS (Integrated Database Management System
Use Cases: Telecommunications, Manufacturing.

Pros and Cons of Each DBMS


DBMS Type Pros Cons
Strong consistency and integrity with ACID
RDBMS (Atomicity, Consistency, Isolation, Durability) Difficult to scale horizontally
compliance
Rigid structure, lacks flexibility for complex
Hierarchical Simple, fast access to data data
OODBMS Object-oriented integration, reusable objects Limited adoption, performance overhead
Weaker consistency guarantees, complex
NoSQL High scalability and flexible schema
querying
If the central server fails, the entire system
Easier to manage, maintain, and secure since all data
Centralized and operations are centralized in one location. becomes inaccessible, leading to potential
downtime.
Easily scales by adding more nodes to handle More complex to design, manage, and maintain
Distributed increased data and user load without significant due to multiple locations and the need for data
performance degradation. consistency across nodes.
Reduces upfront hardware costs and allows users to Data security relies on the cloud provider,
Cloud pay only for the resources they consume, making it which can raise concerns about privacy and
economical for many organizations. regulatory compliance.
The complexity of the network model can make
Efficiently handles complex many-to-many
Network relationships, providing flexibility in data modeling.
it challenging for developers and users to learn
and effectively manage the system.

Real-Life Examples
RDBMS: Used by banking systems like Wells Fargo and transactional databases for online stores such as
Amazon. [1]
Hierarchical DBMS: IBM's IMS system is still used in some legacy banking applications for fast transaction
processing. [2]
OODBMS: Used for managing complex data models and object relationships in CAD systems as well as other
multimedia applications.
NoSQL: Facebook and Twitter implement the NoSQL database to handle high volumes of unstructured user
data, with real-time processing and updates. [3]

Conclusion: DBMS for Large-Scale Distributed Systems


For large distributed systems, the most suitable is NoSQL DBMS because it is scalable and flexible enough to
handle unstructured data. Fast data processing and scaling of applications, such as web and content-heavy systems, goes
well with NoSQL databases like Cassandra and MongoDB. [4] But choice also depends on the use case, structure of the
data, and consistency requirements.

Riphah International University


Hafiz Muhammad Saad BSSE-3B Sap ID: 53180

Reference
[1] C. J. Date and H. Darwen, A Guide to the SQL Standard, 4th ed. Reading, MA, USA: Addison-
Wesley, 2000.
[2] S. Gilbert and N. Lynch, “Brewer’s Conjecture and the Feasibility of Consistent, Available,
Partition-tolerant Web Services,” ACM SIGACT News, vol. 33, no. 2, pp. 51–59, 2002.
[3] E. Brewer, “Towards Robust Distributed Systems,” in Proceedings of the Annual ACM
Symposium on Principles of Distributed Computing, 2000, pp. 7–10.
[4] G. DeCandia et al., “Dynamo: Amazon’s Highly Available Key-value Store,” in Proceedings
of Twenty-First ACM SIGOPS Symposium on Operating Systems Principles, 2007, pp. 205–220.

Riphah International University

You might also like