Description
The ordering is persisted in a single multi-valued string property containing the names of the children in the correct order, which is prone to run into property size limits or even document size limits and also may perform poorly.
One concern in particular is the possibility to run into Mongo's document size limit of 16M with long transactions containing many operations that change the ordering (or insert/remove), eventually triggering branch commits that will be stored in a single Mongo document quickly growing in size because of the weird data model used to persist the ordering.