&gt; It looks like even aborted transactions require writes to the database. And every transaction requires at least two writes (the write intent and its consolidation to the key). I don&#x27;t expect good performance here.<p>Isn&#x27;t this kind of needed in case of unexpected network partitions? I&#x27;m thinking of tests like Jespen (<a href="https:&#x2F;&#x2F;aphyr.com&#x2F;tags&#x2F;jepsen" rel="nofollow">https:&#x2F;&#x2F;aphyr.com&#x2F;tags&#x2F;jepsen</a>), if you want to retain full ACID and consistency in worst case scenarios, you&#x27;ll need these kind of slower transactions checks, I may be wrong though.