Data Models

What is a Data Model?

A data model is a collection of conceptual tools for describing data, data relationships, data semantics, and consistency constraints. It provides a way to think about and represent the structure of a database.

Categories of Data Models

1. Hierarchical Model

Data is organized in a tree-like structure with a single root and parent-child relationships. Each parent can have many children, but each child has exactly one parent.

Advantages: Simple for 1:N relationships, fast access following parent-child paths.

Disadvantages: Cannot represent M:N relationships naturally; redundancy if a child has multiple parents.

Example System: IBM IMS (Information Management System).

2. Network Model

An extension of the hierarchical model that allows many-to-many relationships. Data is organized as a graph, where records (nodes) are connected by links (edges).

Advantages: Supports M:N relationships, more flexible than hierarchical.

Disadvantages: Complex navigation; application programs must know the physical structure.

Example System: CODASYL databases.

3. Relational Model

Data is organized as a collection of tables (relations). Relationships between tables are represented using common attribute values (keys), not physical pointers.

Advantages: Simple tabular structure, powerful query language (SQL), data independence, solid theoretical foundation (relational algebra).

Disadvantages: Complex joins can be slow for very large datasets; not ideal for hierarchical data.

Example Systems: MySQL, PostgreSQL, Oracle, SQL Server.

4. Entity-Relationship (ER) Model

A high-level conceptual data model used for database design. It represents data as entities (things), attributes (properties), and relationships (associations between entities).

ER models are typically converted into relational schemas for implementation.

5. Object-Oriented Model

Extends object-oriented programming concepts to databases. Data is stored as objects with:

• Attributes (data)
• Methods (behavior)
• Inheritance (IS-A relationships)
• Encapsulation (hiding implementation)

Example Systems: ObjectDB, db4o, some features in PostgreSQL.

6. Object-Relational Model

A hybrid combining relational and object-oriented features. It supports complex data types, user-defined types, and methods within a relational framework.

Example Systems: PostgreSQL (natively supports arrays, JSON, user-defined types).

Comparison of Models

Most Used Today

The relational model remains dominant for structured data, while NoSQL models serve specialized use cases in large-scale and flexible-schema scenarios.