Techie Madness

On a high level when we input the data into the cache using the named cache it looks like the below image. But if we get into the depth it looks like the below. When we invoke a method on named cache it will delegate the request to the under lying cache service, this cache service takes the responsibility of distribution of data across the nodes and also retrieval of data from the nodes in the cache. One point to be noted here, it is the backing map which takes care of actual storage of the cache. There will be one instance of backing map per named cache per node. Whereas a single cache service is responsible for more than one named cache.  1.       Replicated Cache:   Each cache item is replicated to all the nodes in the cluster; it means that every node which runs the replicated cache service will have the full data to access in that node. In the below diagr...

Coherence*Extend consists of two basic components: a client and a Coherence*Extend clustered service hosted by one or more DefaultCacheServer processes. The adapter library includes implementations of both the CacheService and InvocationService interfaces that route all requests to a Coherence*Extend clustered service instance running within the Coherence cluster. The Coherence*Extend clustered service in turn responds to client requests by delegating to an actual Coherence clustered service (for example, a Partitioned or Replicated cache service). The client adapter library and Coherence*Extend clustered service use a low-level messaging protocol to communicate with each other. Coherence*Extend includes the Extend-TCP transport binding for this protocol which uses a high performance, scalable TCP/IP-based communication layer to connect to the cluster Basics steps of Extend : 1.       Create client side coherence cache configuaration file that inclu...