Hi Kamesh, Here are my answers.
1. You should try loading the data in multithreaded fashion. The easiest way to do this is to extend CacheLoadOnlyStoreAdapter instead of CacheStoreAdapter and implement inputIterator and parse methods instead of loadCache method. This adapter will parallelize loading process automatically. Also if you have several nodes, you can speed up the process with partition-aware approach which is described in [1]. 2. Can you please clarify what you mean here? How objects are linked to each other? What behavior do you expect when you change one of them? 3. With Ignite you can execute any code on server nodes using Compute Grid [2]. Your tasks and/or closures can access data, so you will be able to do any required processing. Will this work for you? 4. No. Core functionality is the same in all editions, including third-party builds provided by GridGain. [1] https://apacheignite.readme.io/docs/data-loading#section-partition-aware-data-loading [2] https://apacheignite.readme.io/docs/compute-grid -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Need-to-effect-cache-at-time-of-changes-made-in-database-tp2182p2207.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
