> we will have hundreds to thousands of caches This is not a very good idea [1], every cache imposes some overhead, and starting/stopping caches is not cheap as well.
Please consider a different approach where data is grouped into a smaller number of caches. > When we insert a record in cache1, then we want to add/update that record into cache2 What's the idea behind that? Can you keep all the data for the given record in one cache instead of multiple? [1] https://stackoverflow.com/questions/55297333/does-apache-ignite-support-10-thousands-of-cache On Tue, Jan 19, 2021 at 5:46 PM Jigna <[email protected]> wrote: > Hi, > > In addition to that, We have so many projects. So, we will have hundreds to > thousands of caches at any given time and that the number changes as we add > and remove projects. > > I am not sure in this scenario, which solution suits best, continuous query > or events handling in a service? Would you please help me to understand? > > Thanks, > Jigna > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
