# Data model

Concept · [Technical basics](https://ecosystem.samcarlton.com/technical)

Also called: data models, data modeling, data modelling, schema, database schema

The plan for what information an [app stores](https://ecosystem.samcarlton.com/web-app-mobile-app) and how the pieces relate, such as customers, orders and products and which belongs to which. Getting it right early saves rework later.

**For example:** In a class-booking app's data model, a student has many [bookings](https://ecosystem.samcarlton.com/bookings), and each booking belongs to one class.

## Connects to (8)

- [Database](https://ecosystem.samcarlton.com/database): Organized storage for your app's information, such as users, orders and messages, so it can be saved and looked up later.
- [Join table](https://ecosystem.samcarlton.com/join-table): A database table whose only job is to connect two other tables when items on each side can link to many on the other.
- [ORM](https://ecosystem.samcarlton.com/orm): Object-relational mapping.
- [Data normalization](https://ecosystem.samcarlton.com/data-normalization): Making records consistent so the same thing is always written the same way, and, in database design, storing each fact in only one place.
- [Knowledge graph](https://ecosystem.samcarlton.com/knowledge-graph): A way of storing information as things and the named connections between them, such as 'course A teaches skill B'.
- [JSON](https://ecosystem.samcarlton.com/json): JavaScript Object Notation.
- [Meta box](https://ecosystem.samcarlton.com/meta-box): A panel on a WordPress editing screen with extra fields for a post, such as an event date or a price, beyond the main title and body.
- [Technical requirements document](https://ecosystem.samcarlton.com/technical-requirements-document): A document that explains how a feature will be built: the systems, data and technical choices.

Map view: https://ecosystem.samcarlton.com/data-model