Plurix implements an own consistency model basing on restartable transactions coupled with an optimistic synchronization scheme. The optimistic synchronization scheme avoids explicit locking and therewith deadlock problems. The rollback of transactions is possible by creating before images for modified pages. In the case of a read/write conflict N-1 transactions out of N might be restarted. If a transaction successfully commits it invalidates modified pages and discards local before images. Invalidated pages might be send to other nodes on request.

"Sequential Transaction Consistency" ensures that all nodes have the same view on memory accesses while interleaving of transactions is valid. Memory access always occurs in the original program order.