Design a Key-Value Store with TTL and Transactions

An in-memory key-value store: committed data in a locked store and uncommitted writes in each session's stack of transaction layers, versions validated at the outermost commit, lazy expiry on read plus bounded sweeps from a heap of deadlines, eviction behind an interface, and 4,000 increments from eight threads with none lost.