2 Replies Latest reply on Oct 19, 2009 9:26 PM by Eric Ma

    Infinispan vs. Ehcache

    Eric Ma Newbie

      Currently making a decision between Infinispan vs. Ehcache. Ehcache appears to be somewhat ahead of the curve, with RESTful and standalone servers (see my other post), and support RMI, JMS, and JGroups replication. However, there are a couple of things that I am not very clear about:

      1. Is "Distributed" Ehcache truly distributed or replicated (I want the former)?
      2. Does Terracotta integration add any value above and beyond the standalone server?

      Any insight from the Infinispan team?



        • 1. Re: Infinispan vs. Ehcache
          Manik Surtani Master

          AFAIK EHCache only does replicated (just like JBoss Cache).

          Infinispan is designed primarily as a p2p app, and hence the lack of a server module or connector. However, we do realise that this style of architecture is useful to people and hence the REST server and ISPN-29.

          In terms of network transports, Infinispan currently uses JGroups. RMI and JMS doesn't perform nearly as well for high volume systems, and the benefits (simplicity in implementation) don't really affect the end user (i.e., you). :)

          • 2. Re: Infinispan vs. Ehcache
            Eric Ma Newbie

            If I introduce a RESTful server in the mix, will the cache remain distributed? I assume if all cache read/write go through the server, then eventually all cached data will have a copy in the server node. Am I right on that?