JBoss TreeCache vs PojoCache when using invaludation rather than replication -


we setting jboss cluster , building own distributed cache solution built upon jboss cache (cant use 2nd level cache orm layer in our case). want use invalidation , not replication cache mode. far can see after (very) little testing both solutions seem work, objects put cache , objects seem evicted when updated on of servers. leads me believe pojocache aop instrumentation needed when using replication can replicate updated field values , not whole objects. correct here or there other advantages using pojocache on treecache in our scenario? , if pojocache have advantages, still need aop instrumentation , annotate our entities @pojocacheable (yes, using jbcache 1.4.1) since not using relication?

regards jonas heineson

pojocache has ability through aop to:

  • only replicate changed fields , not whole objects. makes difference if e.g. person object containes huge image of person , change password
  • detect changes , can automatically put them on list replicated.

treecache (plain) not need aop, can not replicate individual fields or detect has changed need trigger replication yourself.

if don't replicate, points irrelevant.

iirc, don't need @pojocacacheable annotation pojo cache - without it, need specify classes enhanced in different way.

i have feeling if not replicating, plain treecache enough.


Comments

Popular posts from this blog

apache - Add omitted ? to URLs -

redirect - bbPress Forum - rewrite to wwww.mysite prohibits login -

php - How can I stop spam on my custom forum/blog? -