OSB Result Caching Best Practices

Different caching strategies that we have are :
 Out-Of-Process

             In-Process

§           

         In In-process strategy,  we are using the same JVM memory for cache,JDBC, JMS,transformations, Proxy Services and Business Services. If we increase our cache usage to a high volume, we can potentially run out of memory and thus compromise all other services in the Enterprise Service Bus, even the ones that are not using cache features. 

if your osb application consumes more heap space with Result Caching then we can go with out-of-process. In out-of-process Coherence server can be set up to run in their own JVMs to hold the cached results. They are termed “out-of-process” because they execute in a JVM different from the OSB JVM. The technique here is to allocate data off the OSB JVM letting the Coherence servers use their own heap space without affecting the heap space OSB uses to process messages. This technique is also called off-heap caching.