[jboss-dev-forums] [Design of JBossCache] - Evolution of TcpDelegatingCacheLoaders/TcpCacheServers

[akluge]

Hi,

  I am currently investigating the incorporation of JBC into an existing, large, environment. In the near future, I expect to touch on many issues from JBCACHE-789 (Proxy), 1259 (HA), and possibly 1262 (Executor).

  The use of JBC centers on the FarCaching pattern mentioned in the wiki,  but with some additions.  As a proof of concept, I have a cluster of TcpCacheServers, along with several stand alone caches, with a custom cache loader. The cache loader extends the AbstractCacheLoader to implement a distributed hash table. It contains several TcpDelegatingCacheLoaders, and delegates requests to the appropriate one as determined by a consistent hashing algorithm.

  I am looking at a number of issues now, such as event notifications, failovers and recoveries, and generally improving the structure.

  I thought it would be useful to touch base with whoever is active on these fronts on the JBC side, and hopefully some of what I do will be useful for a wider audience over time. If I know the JBC design goals, I might be able to work them in while addressing my own goals.

  One of the first things I want to look at using reader and writer threads for the TcpDelegatingCacheLoaders and possibly the TcpCacheServers. My main desire here is to allow these classes to be easily extended to handle events. This leads to an immediate question: how sensitive should I be to backwards compatibility issues? I am quite tempted to rebuild this CacheServer/Cacheloader pair from the ground up.

                               Thanks for sharing your thoughts,
                                                                           Alex


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207788#4207788

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207788