Hi Raj, Affinity collocation is an essential part of distributed caches and databases like Ignite that allows to store related data on the same cluster machine and, thus, making performance of particular operations much faster.
These resources will help you to grasp the idea and usefulness of this concept: - https://www.gridgain.com/resources/blog/apache-cassandra-vs-apache-ignite-affinity-collocation-and-distributed-sql - https://www.gridgain.com/resources/webinars/in-memory-computing-essentials-architects-and-developers-part-2 - https://www.gridgain.com/resources/webinars/scale-out-and-conquer-architectural-decisions-behind-distributed-in-memory — Denis > On Jan 20, 2018, at 9:29 AM, Rajarshi Pain <rajarsh...@gmail.com> wrote: > > Hello, > > I am trying to explore different functionality offered by Ignite (2.3) but > this AffinityKey concept is not quite clear to me so need some suggestion > from Ignite experts. > > we are having a scenario where we will load all static data from DB to cache > and do various validations for the incoming messages. > > will AffinityKey be useful in this scenario ? can we except better > performance that an implementation without AffinityKey ? > > We will run a multi-node, multi-threaded application > > -- > Regards, > Raj
