Currently we are storing large trees that require fast writes and are using the Materialized Path approach which stores the path for each node in a field that is indexed and searched using regex. This approach is great for fast reads and writes which is what we need. We have already tried taking a nested set approach but the amount of writes and thrashing that occurs for reparenting is extremely slow.
We like our current approach with the materialized path, but we will soon be bumping into the limit of a indexed field size of 1014bytes. Is there a way to increase this limit or is it being increased for Mongo 3.0
Jake Dempsey