
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
- DNS help
I need the appwrite console in api.xxxxxxx.com and a next.js website in xxxxxxx.com how can i achive this
- Appwrite sites domain not updating
Whenever I commit and sync changes to my github repo which has my website. If i try to go to the domain that was given to me "https://nameofwebsite.appwrite.net...
- Sites - ETA
Hi I've requested Sites and I am currently on waiting list. Whats average ETA to be this available from requesting it? I am on Free tier atm.
