It has scalability, yeah, but I'd need to index a lot of data. I still don't know if it's the best for my use because sometimes I have to work in small sections and other times I need the whole picture (join statements), and Mongo doesn't offer that flexibility.
Good Overviews
Generally speaking you're making a decision between fast read times (e.g. nested set) or fast write times (adjacency list). Usually you end up with a combination of the options below that best fit your needs. The following provides some in depth reading:
One more Nested Interva...
I want to be able to go to "pear" and then see all of the related fruits (apple, peach) and see that another category is "veggies" that's related in the category of "food"
The issue is, I'm going to have a lot of top-level entities like "food" that will be created at runtime so I'm afraid MongoDB is going to get swamped.