MongoDB中存储用户专属重复字段（如收藏电影）的合理模式咨询

Hey there! As someone who’s built plenty of user-centric MongoDB systems, let’s walk through the best ways to store your user accounts and their favorite movies. Your use case is super common, and MongoDB’s flexible document model has great options for this—let’s cover the two main patterns, their pros/cons, and examples.

1. Embedded Document Pattern (Recommended for Most Cases) #

This is the go-to approach when each user’s movie collection is relatively small (think thousands of entries max) and doesn’t need to be shared across multiple users. You’ll nest the user’s favorite movies directly inside their user document.

Example Document #

// users collection document
{
  "_id": ObjectId("60d21b4667d0d8992e610c85"),
  "email": "user@example.com",
  "password": "$2a$10$Z8Hk...", // Always store HASHED passwords (use bcrypt, Argon2, etc.)
  "favorite_movies": [
    {
      "title": "星际穿越",
      "genre": "科幻",
      "release_year": 2014
    },
    {
      "title": "肖申克的救赎",
      "genre": "剧情",
      "release_year": 1994
    }
  ]
}

Why This Works #

• Fast queries: You can fetch a user and all their favorite movies in a single database call:

  db.users.findOne({ email: "user@example.com" })
  

• Easy updates: Adding a new favorite movie is straightforward with the $push operator:

  db.users.updateOne(
    { email: "user@example.com" },
    { $push: { favorite_movies: { title: "盗梦空间", genre: "科幻", release_year: 2010 } } }
  )
  

Caveat #

MongoDB has a 16MB limit per document. If you expect users to collect tens of thousands of movies, this pattern might hit that limit—then you’ll want to use the reference pattern instead.

2. Reference Pattern (For Large/Shared Datasets) #

Use this if movies will be shared across many users (e.g., multiple users favoriting the same movie) or if user collections grow extremely large. You’ll split data into two separate collections: users and movies, then reference movie IDs in the user document.

Example Collections #

movies Collection

{
  "_id": ObjectId("60d21b8667d0d8992e610c86"),
  "title": "星际穿越",
  "genre": "科幻",
  "release_year": 2014
},
{
  "_id": ObjectId("60d21b9667d0d8992e610c87"),
  "title": "肖申克的救赎",
  "genre": "剧情",
  "release_year": 1994
}

users Collection

{
  "_id": ObjectId("60d21b4667d0d8992e610c85"),
  "email": "user@example.com",
  "password": "$2a$10$Z8Hk...",
  "favorite_movie_ids": [
    ObjectId("60d21b8667d0d8992e610c86"),
    ObjectId("60d21b9667d0d8992e610c87")
  ]
}

Querying with References #

To get a user and their favorite movies, use the $lookup aggregation stage to join the two collections:

db.users.aggregate([
  { $match: { email: "user@example.com" } },
  {
    $lookup: {
      from: "movies",
      localField: "favorite_movie_ids",
      foreignField: "_id",
      as: "favorite_movies"
    }
  }
])

Why This Works #

• No data redundancy: You only store each movie once, even if 1000 users favorite it.
• Document size control: The user document stays small even with thousands of favorites, since you’re just storing IDs.

Caveat #

Queries are slightly slower because you need to join collections, and updates to movie details (e.g., correcting a title) will automatically apply to all users who favorited it—this is a pro or con depending on your needs!

Which Pattern Should You Choose? #

• Go with embedded documents if:
  • Individual users won’t have more than ~5k favorite movies.
  • Movie details are unique to the user (or you don’t need to share/update them across users).
• Go with references if:
  • Movies are shared across many users.
  • You expect users to collect tens of thousands of movies.

Critical Reminder #

Never store plain-text passwords! Always hash them with a secure algorithm like bcrypt or Argon2 before saving to the database.

内容的提问来源于stack exchange，提问作者Prasad Khutemate