Hi, Replicated cache is used in cases when you need to store a small data set or data set that is not updated frequently. In banks area dictionaries with exchange rates are usually stored in replicated caches because they are not updated frequently and they are relatively small. All the operations that are performed on server nodes and use exchange rates in their calculation won’t need to go to some primary node to load an exchange rate because all the data will be located locally. If the exchange rates are stored in a partitioned cache then the performance of the operations will worse.
Hope know the use case of replicated caches is much more clear to you. Next, answering on some of your questions. > As for the computing job, I would use the affinity collocation, so my job > will utilize the local cache anyway. If you use compute.affinityRun(…) then by default the job will be executed on a node that holds primary copy of the key. > If I use the Ignite in the client mode (which means my client node doesn't > hold any data), it still has to do the network call to the primary node of > the REPLICATED cache. Correct. If you want to cache some data on the client node then you can use near caches - https://apacheignite.readme.io/docs/near-caches <https://apacheignite.readme.io/docs/near-caches> Regards, Denis > On May 13, 2016, at 8:10 PM, zshamrock <[email protected]> wrote: > > Alexei, but I still trying to understand the use case for the REPLICATED > cache. > > As for the computing job, I would use the affinity collocation, so my job > will utilize the local cache anyway. > > If I use the Ignite in the client mode (which means my client node doesn't > hold any data), it still has to do the network call to the primary node of > the REPLICATED cache. > > So, what are the use cases for the REPLICATED cache. Do I miss anything? > > Thank you, Alexei. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/How-REPLICATED-cache-is-more-performant-comparing-to-PARTITIONED-tp4915p4935.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
