Yes, you&#x27;re right. Now where that paper finishes is pretty much where GoshawkDB starts. Because with GoshawkDB, the server controls the object UUId, you can push as much entropy in there as necessary so the problem identified in the paper is gone. However, ultimately what GoshawkDB ends up generating is basically a set of numbers that you interpret as a way to construct an order of the different nodes (it&#x27;s the path down the tree, as described in the paper). This set of numbers you could intentionally change in order to change the load balancing to exploit locality.<p>So yes, currently it&#x27;ll rigorously enforce a uniform balancing. However, it should be possible to move objects around if&#x2F;when necessary. I doubt that&#x27;ll be in for 0.2 though!