
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
- CSV Not Importing
We don’t seem to having any luck importing a simple .csv file. The import function acts like it’s working but no data imports or is shown in the collection The...
- Appwrite Cloud Custom Domains Issue
I’m trying to configure my custom domain api.kondri.lt (CNAME pointing to appwrite.network., also tried fra.cloud.appwrite.io with no luck ) but encountering a ...
- Persistent 401 Unauthorized on all authe...
Hello, I'm facing a critical 401 Unauthorized error on my admin panel app and have exhausted all debugging options. The Problem: When my React app on localhos...
