
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
- Creating a relationship with nested obje...
{ "data": { "name": "DiDi", "type": "Software Development", "userJobs": [{ "$id": "68cbf1e2003612fb13ca", "j...
- Realtime integration with SSR auth
Hey, I have a nextjs website with SSR auth, works great. I use a session client for user verification and an admin client with API key. Both is used with node-...
- Adding "name" column to table creates 2-...
As stated, im adding the "name" column to one table, it adds 4 duplicates. In another table it adds 3 duplicates, and when I delete 1 of them, all duplucates di...
