ultimately, there are tradeoffs and it's up to you.
you can research database normalization, but in practice, databases aren't always normalized because it depends on the use case
Votes
0
Replies
12
Participants
Unknown
Messages
13
ultimately, there are tradeoffs and it's up to you.
you can research database normalization, but in practice, databases aren't always normalized because it depends on the use case
Rank 3: Container
[SOLVED] Scalable database design
@loup no need to delete your posts. it can be helpful for others to see
Rank 3: Container
Sry I’ve miss clicked… idk how to undo
i don't think you can undo a delete. no worries
I'm interested in your final decision
Rank 3: Container
Well I dont have the final decision because I dont have enought experience in dev
Rank 3: Container
But my actual setup is one collection per functionnality
Rank 3: Container
But its so hard to maintain consistency between each document
Rank 3: Container
There is an exemple about my database design but isnt really good
Rank 3: Container
Rank 3: Container
Maybe I can create another table movie_actions which is a collection connected to movie_liked, movie_review, movie_rated, movie_watched, movie_watchlisted, movie_guidelisted. Like this I can only call the movie_actions to get all action from user about a movie
Rank 3: Container
But that make a lot of collection