That&#x27;s the intuition behind systems like Flake (<a href="https:&#x2F;&#x2F;github.com&#x2F;boundary&#x2F;flake" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;boundary&#x2F;flake</a>) and its predecessors.<p>In systems like Flake you are able to get a useful roughly-ordered property which is good for generating ID&#x27;s and organizing things like activity feeds. Things will be mostly sorted by time by encoding the time in the most significant bits, but they will be fuzzy because of machine and sequence ID&#x27;s in the LSB&#x27;s. You will get monotonically increasing ID&#x27;s per-process because each one spinlocks locally against backwards drift, but you&#x27;re not guaranteed to get monotonically increasing ID&#x27;s globally across all processes. One process&#x27; time might drift forward, or you might have two ID&#x27;s at the same time but the instance with the higher machine ID responded first.