Data Model

Data Model: How Your Database Is Organized

A data model is the method used to represent how data is structured inside a database—it sets the rules for how information connects.

Why it Matters

• Helps business and tech teams speak the same language
• Guides data integration, migration, & architecture decisions

Schema vs. Data Model—What’s the Difference?

• Data Model: The blueprint or plan; shows how data and relationships are organized (think flowcharts, diagrams, concepts).
• Schema: The building itself; the actual specification and implementation of tables, columns, keys—created using the chosen data model.

“Data Model is the Blueprint; Schema is the Building.”

Types of Data Models

🔸 Hierarchical Model

• Tree-like parent-child relationships
• Used in early database systems

🔸 Network Model

• More flexible: records can have multiple parent-child connections
• Adds complexity compared to hierarchical

🔸 Relational Model

• Data organized in tables (rows & columns)
• The most widely used model today
• Example: Customer table with name, address, phone fields

🔸 Entity-Relationship (ER) Model

• Designs database visually with entities (objects), attributes (properties), relationships
• Used for conceptual database design

🔸 Object-Oriented Model

• Combines database concepts with object-oriented programming
• Data represented as objects with attributes & methods (supports inheritance, encapsulation)

🔸 NoSQL Data Models

• Various structures to fit diverse needs
  • Document-oriented: e.g., MongoDB
  • Key-value: e.g., Redis
  • (Also includes graph & columnar models)