title: MongoDB One to Many Relationship
body: <p>I’m starting to learn MongoDB and I at one moment I was asking myself how to solve the “one to many” relationship design in MongoDB. While searching, I found many comments in other posts/articles like ” you are thinking relational “.
  Ok, I agree. There will be some cases like duplication of information won’t be a problem, like in for example, CLIENTS-ORDERS example. </p>
  
  <p>But, suppose you have the tables: ORDERS, that has an embedded DETAIL structure with the PRODUCTS that a client bought.
  So for one thing or another, you need to change a product name (or another kind of information) that is already embedded in several orders.</p>
  
  <p>At the end, you are force to do a one-to-many relashionship in MongoDB (that means, putting the ObjectID field as link to another collection) so you can solve this simple problem, don’t you ?
  But every time I found some article/comment about this, it says that will be a performance fault in Mongo. It’s kind of disappointing </p>
  
  <p>Is there another way to solve/design this without performance fault in MongoDB ?</p>