The Hot Rod protocol v 2.6 is introducing transactions, this might be available in Infinispan 9.2

The transaction context is managed by the client and created a Xid

A read operation:

• if the key doesn't exist in the context, it's retrived from the server
• if the key is in the context it's returned from there. Similar to Repeatable Read ?

Writes spanning multiple caches are possible, but it will introduce additional latency during the prepare phase as they will have independent TX contexts.

A node failure doesn't affect the transaction state: server side state is replicated among multiple nodes.

A full design document is being proposed here: https://github.com/infinispan/infinispan-designs/pull/6

N.B. changes on the server won't affect any query result until the transaction is committed.
This implies that when we normally need to "flush" this would be a pointless operation, and we need to keep in mind that the need can't be addressed (at this point).