-
1. Re: Understanding (invalidation) cache behavior for a REST client
wesmith80 Apr 29, 2015 9:21 PM (in response to wesmith80)Basically I'm trying to decide between HotRod and REST clients and my understanding is that with HotRod (for a distributed cache) the client has knowledge of what keys are in what node in the cluster, so a cache miss is avoided.
-
2. Re: Understanding (invalidation) cache behavior for a REST client
rvansa Apr 30, 2015 4:15 AM (in response to wesmith80)In distribution mode, if the key is not on local node (and it should not be hashed there), the entry is retrieved from remote node rather than going to the database.
In invalidation mode, you would go to the database if it's not found in memory.
If you can use HotRod, use HotRod, this is the native and most optimized protocol. REST would be recommended if the client is e.g. in JavaScript where you could not use HotRod.
-
3. Re: Understanding (invalidation) cache behavior for a REST client
wdfink Apr 30, 2015 6:56 AM (in response to wesmith80)I would recommend HotRod as it knows which node to ask for a key. Also there is no need for a loadbalance as HR will do the work.
Decision for Invalidation or Distribution depends on your use-case and what approach (REST, HR) you use. Invalidation can be slow if you doing a lot of writes.