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
- I’m facing an issue with deployments on ...
Hi Appwrite Support, I’m facing an issue with deployments on Appwrite Sites. A few days ago (around 3–4 days back), everything was working perfectly. My deplo...
- Export, Import or Migration giving this ...
As you can see in yhe screenshot i am not able to export any data or export the data from tables. Also it is affecting the migration from appwrite to appwrite h...
- Project auto-blocked after load testing ...
Hi team 👋 My project has been automatically blocked with the message: "Project is currently blocked — Access to this project is restricted. Contact support if...