Which is better to use - EHCache, OSCache or Swarmcache

[twoencore]

I had alot of success with using OSCache on a previous project, the documentation was good.. an advantage i saw over EHCache was OSCache ability to return stale content while the cache is being updated... EHCache has a limitation that blocked thread writes while being updated..which made a bottle neck when doing "Method level" caching...with OSCache would send back the stale content while the cache is being updated from another thread.

OSCache also supports distributed cache clustering via JMS.


also your not tied to a container(JBossTree)

[tgautier]

I'll try. Firstly, my requirements and goals are to operate a production system on commodity hardware, and safeguard data that is extremely valuable to our customers.

We also can't handle the system load on one box, so operate multiple boxes behind an Apache front end.

So, I've decided we need transactional clustering to deliver the above requirements.

The only choice seems to be JBoss TreeCache, which works pretty well.

I think the next JBoss TreeCache release supports eviction from the cluster as opposed to replication across the cluster which will be good.

I'm hoping it will scale reasonably well since we're scheduled to do a country wide sales and marketing rollout around April so will likely have some interesting performance figures to share by then.

Regards,

Sorry to resurrect this thread from the dead - but I am quite curious after two years how things turned out. Did you end up using transactions w/TreeCache? Did it scale for you? How has it been in operation?

Thanks,

Taylor Gautier
Product Manager, Terracotta