Scribd
Upload
2 views

Lecture 4 Database Models

The document provides an overview of various database models, including Hierarchical, Network, Relational, Object-Oriented, and Document-Oriented models, detailing their structures, advantages, and disadvantages. It emphasizes the importance of choosing the right model based on specific use cases, performance needs, and scalability requirements. Each model serves different types of data organization and manipulation, highlighting the diversity in database design.

Uploaded by

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

Lecture 4 Database Models

The document provides an overview of various database models, including Hierarchical, Network, Relational, Object-Oriented, and Document-Oriented models, detailing their structures, advantages, and disadvantages. It emphasizes the importance of choosing the right model based on specific use cases, performance needs, and scalability requirements. Each model serves different types of data organization and manipulation, highlighting the diversity in database design.

Uploaded by

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

Introduction to Database Models

A database model defines the logical structure of a database and determines how data is stored,
organized, and manipulated. It acts as a blueprint for designing databases.

Types of Database Models

1. Hierarchical Model

Data is organized in a tree-like structure.

Each parent can have multiple children, but each child has only one parent.

Example: IBM's Information Management System (IMS).

Pros: Fast data retrieval for hierarchical data.

Cons: Complex and rigid structure, difficult to modify.

Example:

Company (Parent)

├── HR Department (Child)

├── Employee 1

├── Employee 2

├── IT Department (Child)

├── Employee 3

├── Employee 4

2. Network Model

Data is organized as records connected by links (many-to-many relationships).

Uses pointers to navigate between records.

Example: Integrated Data Store (IDS).

Pros: More flexible than the hierarchical model.

Cons: Complex to design and manage.


3. Relational Model (Most Common)

Data is stored in tables (relations) consisting of rows (tuples) and columns (attributes).

Tables are linked using primary keys and foreign keys.

Example: MySQL, PostgreSQL, Oracle.

Pros: High flexibility, easy querying with SQL.

Cons: Performance can be slow for large-scale applications.

4. Object-Oriented Model

Data is represented as objects, similar to object-oriented programming.

Objects contain attributes and methods.

Example: MongoDB, ObjectDB.

Pros: Suitable for complex applications (e.g., multimedia, CAD).

Cons: More complex than relational databases.

5. Document-Oriented Model (NoSQL)

Stores data as JSON, BSON, or XML documents.

Suitable for semi-structured or unstructured data.

Example: MongoDB, CouchDB.

Pros: Scalable, schema-less, handles big data well.

Cons: Not ideal for transactions requiring strong consistency.

Choosing the Right Model

For structured, transactional data → Relational Model

For hierarchical data → Hierarchical Model

For complex relationships → Graph Model


For high-speed key-value storage → Key-Value Model

For unstructured or big data → Document-Oriented Model

Conclusion

Each database model has strengths and weaknesses. The choice depends on the use case, performance
needs, and scalability requirements.

You might also like