Entities
Business objects that usually become database tables, such as users, orders, and products.
ERD diagram guide
An ERD diagram documents tables, columns, keys, and relationships so teams can agree on data structure before implementation. Use it when turning requirements into a data model or reviewing an existing schema.
Definition
ERD stands for Entity Relationship Diagram. It shows the data objects a service manages and the relationships between them, helping developers decide which tables are needed and how records reference each other.
Elements
Business objects that usually become database tables, such as users, orders, and products.
Column-level data including names, types, required flags, defaults, and uniqueness.
Primary keys and foreign keys that make rows and relationships reliable.
The direction and cardinality between entities, such as one-to-many or optional one-to-one.
Workflow
List nouns the service must store, then remove duplicates or overly broad candidates.
Add columns such as id, status, and created_at, then mark primary keys, foreign keys, uniqueness, and nullability.
Represent rules such as whether one user can have many orders or whether each order must have a user.
Check repeated columns, many-to-many relationships, derived values, and the flows your API will query often.
Treat the ERD as a living design document that changes with the product.
Example
A small commerce domain can start with users, orders, order_items, and products. Instead of connecting orders and products directly as many-to-many, use an order_items table to preserve quantity and price-at-order data.
ErdForge
ErdForge gives you a canvas for ERD editing, team sharing, Oracle/PostgreSQL/MySQL/MariaDB/SQLite type options, JSON and SQL export, and MCP integration for AI-assisted diagram drafts.