Browse Prior Art Database

Method and Program to Alias Cached Objects in a Distributed Caching Environment

IP.com Disclosure Number: IPCOM000035501D
Original Publication Date: 2005-Jan-21
Included in the Prior Art Database: 2005-Jan-21
Document File: 2 page(s) / 36K

Publishing Venue

IBM

Abstract

Method and program to alias cached objects in a distributed caching environment

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Method and Program to Alias Cached Objects in a Distributed Caching Environment

J2EE application developers often need to store an object in distributed cache by one key and retrieve the same object by using two or more different keys. To reference a cached object by other than the key used to created the object, a developer can maintain a table of cached object keys mapping them to the desired alternate names and placing duplicate entries into cache. This is not a problem in a non-distributed environment because there is only one copy of the cached object in memory. This approach has multiple problems in a distributed caching environment. The application developer has to ensure the mapping table is distributed to peer caches to ensure when one entry is invalidated all aliased entries are also invalidated. Also, two ( or more ) copies of the data will unnecessarily be sent and reside in the remote caches. Cache consistency can become compromised. Increased network bandwidth is needed to accommodate the sending of duplicate content and the mapping table. Memory requirements are increased on remote caches due to the duplication of content. This paper describes a method to eliminate these problems by introducing cache entry aliases in the core cache. Alias cache entries allow developers to seamlessly reference cached objects in a distributed environment by either the original name or by an alias name.

The idea is to leverage existing Websphere Application Server Dynamic Cache function and add the ability to manage alternate cached object keys using alias names. This is accomplished by storing alias information in existing core Dynamic Cache. Dynamic Cache will share information with peer caches to manage the synchronization of alias names on all servers within the cluster.

Using this method removes the overhead of managing and distributing mapping tables in the user's code. This will simplify and reduce the required code in the particular J2EE application. Using alias entries also reduces the payload size and improve network utilization as well as...