88 ) Types of Data Models

 

Types of Data Models

Data models provide a formal way to describe how data is organized, structured, and related in a database system. They are generally categorized into three main conceptual levels, followed by specific logical implementation types.

1. Conceptual Data Model

• Purpose: High-level business view created by data architects and stakeholders. It defines what data is needed, focusing on core business entities and their relationships without any technical implementation details.

• Characteristics: No attributes, no data types, and no primary/foreign keys defined.

2. Logical Data Model

• Purpose: Bridges the gap between the conceptual and physical models. It defines the structure of data and the relationships between entities in more detail, independent of any specific database management system (DBMS).

• Characteristics: Includes all entities, attributes, primary keys, and foreign keys. Data types are generally specified.

3. Physical Data Model

• Purpose: The actual database-specific implementation of the model. It shows how the data will be stored within a specific DBMS (like SQL Server, Oracle, or PostgreSQL).

• Characteristics: Includes table names, exact column data types, indexes, constraints, partitions, and storage settings.

Specific Logical & Structural Types

Within these conceptual levels, data models are structured using different architectural paradigms:

1. Relational Model

   • Data is organized into two-dimensional tables (relations) consisting of rows and columns. Relationships are established using primary and foreign keys. This is the standard for most transactional (OLTP) applications.

2. Dimensional Model (Star / Snowflake Schema)

   • Optimized for data warehousing and analytical (OLAP) reporting. It separates data into measurable events (Fact tables) and descriptive context (Dimension tables).

3. Data Vault Model

   • Designed for enterprise-scale data integration, auditability, and historical tracking. It splits data into three core components: Hubs (business keys), Links (relationships), and Satellites (descriptive attributes and history).

4. Hierarchical Model

   • Organizes data in a tree-like structure with a parent-child relationship, where each child node has only one parent. (Older model, foundational for legacy systems).

5. Network Model

   • Similar to the hierarchical model, but allows a child node to have multiple parent nodes, forming a complex graph structure of relationships.

6. NoSQL / Non-Relational Models

   • Designed to handle unstructured or semi-structured data at scale. Key types include:

     • Document Model: Stores data as JSON/BSON documents (e.g., MongoDB).

     • Key-Value Model: Stores data as simple key-value pairs (e.g., Redis).

     • Graph Model: Uses nodes, edges, and properties to represent and store highly interconnected data (e.g., Neo4j).