
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

[SOLVED] Scalable database design

@loup no need to delete your posts. it can be helpful for others to see

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

Well I dont have the final decision because I dont have enought experience in dev

But my actual setup is one collection per functionnality

But its so hard to maintain consistency between each document

There is an exemple about my database design but isnt really good


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

But that make a lot of collection
Recommended threads
- API Endpoint to Verify Password.
I have 2 use cases where i need to verify a users password outside of login, e.g. Updating user account data (such as name, or prefs, or data in a users databa...
- search collection by document ID
How to filter or search collection for a document using document ID, I can't find this item on the filter menu
- Database Migration/Sync Between Two Proj...
Overall The migration failed mainly due to conflicts with existing data (documents, attributes, collections, etc.), exceeding attribute limits, and unsupported ...
