For a write heavy scenario like a shared counter, yes.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213308#4213308
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213308
___
In the same node if Host A updates key value "AAA" to "1" and Host B
simultaneously updated key value "AAA" to "2" would Host A's value be "2" and
B's be "1" after replication? The caches would become out of sync?
So the solution is to use sync cache or switch to a INVALIDATION_ASYNC cache to
You would need to use synchronous replication for such guarantees. A call -
e.g., cache.put() - will not return until the same call is successfully
executed across the cluster. And if a remote instance is attempting the same
thing, it will not complete until the call can be executed across the
