What do you mean by "consistency"?
Have you read any of the transaction literature?
By consistency I mean domain model integrity after I make a commit.
Example: From my client machine I can access/see only one pojo cached from an entire collection and I want to set some property on it.
That property must be unique for all the pojo's in the entire collection, so some checks should be made before I commit. I can't do that check from my client machine because I can't access all the necesary data.
So the checks must be done in another place. How could I do that and still allow transactions from my client machine without involving it in the checking process (because as I said it hasn't all the necessary data).
Seems like you need to write a Resource Manager that knows how to move your state from one consistent state to another. If the service (backend) is the place where the data resides, then that's the place where the consistency check should be done.