3 ms·
Ask HN: Many-to-Many relation by default, is that a good strategy?
Defining entities and their relationships at the start of a project is difficult if the requirements keep changing frequently or are not defined (for example, in a startup setup).
So, in that case starting with Many-to-Many relationship for entities, and then optimising the relationship as things become clear is a good database design strategy?
- PaulHoule 4y agoThat means adding a lot more tables doesn't it?
- _448 4y agoYes, it will add more tables. But as the project progresses, this will be reduced once the relationship between the entities are clear. What I am worried about though is the performance.
- mneil 4y agohttps://www.guru99.com/database-normalization.html https://www.guru99.com/database-normalization.html You usually can get by with 4th normal form but go wild, take it to 11 and it's all you should ever need.
- kasey_junk 4y agoYou could use blob storage until you know the relationships. You lose a lot of the value of relationships in a schema if you don’t know what they are