...
Unlike the current implementation, this option does not require locks to ensure consistency when there are concurrent updates to the same hierarchy. With the example above where user-A moves folder-1 to folder-2 and at the same time user-B moves folder-2 to project-2, both transaction transactions would commit in constant time. In addition, the two moves would trigger two events to be pushed to the asynchronous worker queue (one for each transaction). Both transaction transactions will have been committed by the time the worker receives and processes the second message, therefore the second event will result in a consistent state for all dependent benefactor IDs.
...