...
The four hierarchy related operations would be changed to only update the container and not the dependencies in the hierarchy in a single transaction. After the transaction commits, a message would be sent to a new asynchronous worker. The new worker worker would update each dependency with one an individual transaction per for each update. After the commit of each update an entity update message would be sent to all listeners. This option results in the eventual consistency of benefactor and project ID of each dependent.
...
All four hierarchy related operations will have a constant time complexity. Therefore, updates to large hierarchies will no longer result in web-service timeouts. The This will improve the experience of the user that initiates a large change. However, the experience will change for users waiting for large hierarchies to become consistent. For example, if an ACL is added to a folder with 20K files to grant user-A access, user-A would need to wait for all of the files in the folder to become visible. In fact, user-A might only see a few files immediately after the ACL event, and subsequent refreshes of the view would reveal more files.
...