The answer
You realize later you need a missing field or constraint. Now you migrate the collection, update every query, update the controller, and the frontend. A few hours of design would have saved weeks of rework.
Why You Should Design the Schema Before Coding
What happens if I skip schema design and start coding?
More FAQs in Why You Should Design the Schema Before Coding
Because every layer depends on the schema. Once code is written against a schema, changing it forces changes in controllers, middlewares, validators, and frontend. Schema changes cascade through the codebase.
Collections (entities), fields, types, constraints (required, unique, default, enum), indexes, and relationships (ref vs embed). All of these are hard to change after code is written.
Use ref for one-to-many with large N (e.g., user and messages). Use embed for small, tightly coupled data that always loads together (e.g., an address inside a user). Embedding is fast but bloats documents; ref keeps them small.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.