1 of 1 people found this helpful
Re 1. Slightly slower because with replication it needs to serialize the key and the value, before doing a fire-and-forget to the network in prepare. With invalidation, only the key needs to be marshaller.
Re 2. We implemented single lock ownership, so the locks are aquired in a single node, but all nodes aquire the locks on a specific node depending on the key.
Re 3. Apply locally and send it to the other nodes in fire-and-forget style
Re 4. As long as you use REPETEABLE_READ and have writeSkew enabled and you use transactions, that conflict will be discovered. However, if this is likely to happen in your system, I would recommend against using asynchronous modes.
Re 5. Yes, see previous point.
Re 6. It's independent of PL or OL.
Re 7. Which combination?