Write through? You mean you want a cache plugged with a cache store, and write through to it?
The rest of bits look sensible, but it's not clear how you're planning to access Infinispan, whether in embedded (in-memory) or remote way.
There's plenty of info in https://docs.jboss.org/author/display/ISPN/User+Guide, particularly around the server module pages.
Thanks for the respsone.
The ISPN is going to be embeded.
The whole idea is to have the data be replicated/distributed among the nodes. The cache store (data store) is on each node. I.e., there is no common data store (such as a database behind, which is we want to get rid of).
Other types of implementation I looked at such as XtremeFS (http://www.xtreemfs.org/). I feel we could achieve what XtremeFS with ISPN at the application level instead of FileSystem level.
Right, so if you're not using a cache store, I don't understand what you mean by write-through, because in caching terms, that's normally used to talk about a backing cache store, and how you write through it.
If you're talking about write-through to other nodes in the cluster, see the section on cache modes in the guide.
In terms of cache store, I am thinking using FileSystem cache store, in this case.
Yes, I'd like to have any changes to the cache written out to FileSystem on each node.
It's not clear to me how to handle data sync when a new node joins the cluster, or a node craches and rejoins the cluster.
I am going to re-read those sections on cache mode. Thanks.
When a node joins the cluster, state transfer can be used so that new joining node can retrieve all data on startup from other nodes in the cluster. If you use sync replication, it's enabled by default. Alternatively, you can disable state transfer and instead use a cluster cache loader to retrieve data lazily.