Continuous Queries [1] are designed specifically for use cases like that - to handle cache updates efficiently, please use them instead of Events.
You can subscribe to local and remote cache updates, and define a remote filter if necessary. [1] https://ignite.apache.org/docs/latest/key-value-api/continuous-queries On Mon, Jan 18, 2021 at 9:44 PM Jigna <[email protected]> wrote: > Hi Pavel, > > I really appreciate your help. I will try to explain my scenario: > > 1. When we insert a record in cache1, then we want to add/update that > record > into cache2. > 2. For that, we want to listen the cache event and the listener will > identify the data and either inserts or updates that record into cache2. > > Similarly, we have other caches like cache3 and cache4. So when we insert > the record into cache3 or cache4, then we want to insert/update that record > into cache2. > > Now, the cache events are generated on the server node and I want to write > a > listener service on the server node, which will run the above logic. We use > c# for our development. > > What should I do in this case? Would you please help me? > > Thank you, > Jigna. > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
