How do you typically handle list ordering without creating a nested document in an array field of the parent document? Storing a massive amount of sub-documents under a parent that can all be updated by a client seems like a really quick way to kill performance.For example, if I have a book object, and a page object - having 200+ pages nested under the book object seems like a terrible idea. So do you have an order field on each page object, and when a page is removed - do you go through ALL the pages linked to that book and update their new order? This again seems like a quick way to kill performance.Thoughts?Thanks!Edit: Grammar is hard
Submitted February 14, 2020 at 10:20PM by grumpyrumpywalrus
No comments:
Post a Comment