Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7196665
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T20:49:17+00:00 2026-05-28T20:49:17+00:00

So I am creating a model for a forum. Think thread and a bunch

  • 0

So I am creating a model for a forum. Think thread and a bunch of comments where. Thread has many comments. In RDBMS world, I would design this as such

Thread --has many--> Comment
id                   id
user_id              thread_id
                     user_id 

Now, I guess, with this, the data/schema would follow one of the many normal forms (I forgot which). And I think this is the most sensical way to do it. However, when it comes to doing this in NoSQL world (MongoDB), what would be the best way to design this relationship? I could almost do it in the RDBMS way, but I would lose the advantage of using embedded object. For some reason, I am more inclined to do it like

Thread
_id
user_id
comments => [{_id, user_id, body, created_at}]

What would be the most sensical way to do this I guess that’s what I am asking. And why?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T20:49:19+00:00Added an answer on May 28, 2026 at 8:49 pm

    First off, I hope you have read the docs on Schema Design, which explains with an example similar to yours.

    So, you can embed or link according to your choice. I would embed if the number of comments are expected to be manageable (relatively smaller) and link if there would be too many comments.

    Embedding has the advantage that only one single DB call is required to show a single post/thread and most usually can send just the mongodb response to the browser as is (if client side does the UI rendering). *Note: And adding a comment will require an UPDATE using $push. And do remember that the comment._id has to be created by you, MongoDB won’t auto-create it for you. Any updates of comment data in embedded scenario will require an UPDATE with the $ positional operator.*

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am creating a model binder to use with asp.net mvc. This is what
you would think this would be obvious, but searching through documentation, SAP forums, Googling,
I have a jQuery Model windows which contains a form. On creating of the
I'm looking for a free and simple tool for creating relational model diagrams. All
I am creating a Category model and using the awesome_nested_set plugin (a replacement for
I am creating the domain model in my system. When designing my model objects,
Sometimes the overhead of creating a new model type is annoying. In these cases,
I'm creating my own Group model; I'm not referring to the builtin Group model.
I'm creating a tableless Rails model, and am a bit stuck on how I
I'm regularly creating an XSD schema by transforming a proprietary data model of a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.