4 ms·

This reminds me of Terracotta. Anyone care to contrast the two?

• ShabbyDoo 17y ago
  Terracotta isn't peer-to-peer; it requires one or more management-ish servers. However, it does offer persistence on those servers, so one could use Terracotta in place of a database. Also, Terracotta works in the (historically) Spring-like way of not requiring any modification to an existing codebase. One declares which objects ought to be distributed, and magic just happens (supposedly, I've only been reading up lately). Terracotta does bytecode manipulation on those object references and on Java synchronization blocks to achieve what is explicitly specified with this system. Another project to look into is JBoss's recently re-branded and improved cache: http://www.jboss.org/infinispan http://www.jboss.org/infinispan I've been thinking about a problem lately that will likely require one of these technologies, so I've been especially curious.