title: Designing a MongoDB solution?
body: <p>I'm a RDBMS guy that has a project that I believe will work really well in a MongoDB system.  For different reasons that I think is irrelevant for the questions at hand.</p>
  
  <p>Anyway, my system will be something like the following:</p>
  
  <pre>
  Properties Available
    Houses
      House A
        123 Pine Street
      House B
        456 Main Street
  
  
  Realtors
    Sale
      Leads
        Properties
          House A
            123 Pine Street
        People Involved
          Moe Howard
          Larry Fine
          Shemp Howard
      Budgets
        Operating Budget Items
          $200 rentals
          $400 supplies
  </pre>
  
  <p>As you can see, I have two collections.  One ("Properties Available") will be generated at different times from different sources and will be shared across any number of users.  Most of the content will be static and not change often.</p>
  
  <p>The other collection is "Realtors".</p>
  
  <p>Now, in my old RDBMS world, I would create tables for Leads, People, Budgets, etc.
  However, I think keeping all of the information in one giant "record" would be better.  A "Sale" record would be worked on for a while (weeks perhaps) and then closed.  To me, keeping everything inside that one record is awesome.  Especially since there will be wildly generic and dynamic information stored inside such as websites, notes, photos, etc.</p>
  
  <p>Am I approaching this with the right mind-set?  It's hard for me to let go of the relational model.  </p>
  
  <p>Thanks for any suggestions and tips.</p>