venki sheshgiri wrote: which indeed are consuming lot of App Servers Heap Memory.
This is going to happen with any caching solution. The data needs to be stored somewhere if it's not going to be read from disk or database.
venki sheshgiri wrote:What is the best way to implement distributable cache
It's more commonly called a "distributed search." When you look for an open source or commercial one, it helps to be looking under the name people list it as. You definitely should not "implement" a distributed cache. It is complex and very difficult to get right. This list of open source Java caches
list which are distributed.
venki sheshgiri wrote:[ I would like avoid scenarios where a DB Query or properties file loading are involved.
Some caches work via replication. Which does use network traffic of course, but not a DB query. I can udnerstand why you want to get a potentially expensive DB query out of the picture, but what's wrong with reading from a property file and caching that?