Eager and lazy versioning can be viewed as parallels of write-through and write-back cache policies. Eager versioning is like write-through because it writes straight to memory immediately. However, lazy versioning is like write-back because it writes to a local write-buffer until a commit happens, at which point it flushes to memory.

@pslui88 I think your analogy with write-through and write-back cache was very insightful!

Another benefit of lazy versioning is that there is less coherence traffic since we are only writing to memory once at the end of our transaction and won't have to undo anything committed to memory like eager versioning does.