[infinispan-issues] [JBoss JIRA] (ISPN-2246) Synchronization between Infinispan clusters / simple client connect

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño resolved ISPN-2246.
------------------------------------

    Resolution: Duplicate Issue


You can already achieve this using Hot Rod and RemoteCacheStore, but to support it, you need to deploy some extra pieces of software because we don't natively support back-to-front cache invalidations yet. I did a presentation of this a few months back (https://www.jboss.org/dms/judcon/2012india/presentations/day1track1session2.pdf) and the code used to show these near caches in action can be found within our distribution, in a the near cache demo including instructions how to run it. In this example, we use JMS to provide backend cache to front invalidations.

We already have a JIRA to provide this functionality natively.
                
> Synchronization between Infinispan clusters / simple client connect
> -------------------------------------------------------------------
>
>                 Key: ISPN-2246
>                 URL: https://issues.jboss.org/browse/ISPN-2246
>             Project: Infinispan
>          Issue Type: Enhancement
>            Reporter: Robert Stupp
>            Assignee: Mircea Markus
>
> We are currently thinking about the following architectural scenario:
> * A number of application servers that form an Infinispan clustered cache
> * A "backend" Infinispan cluster with file based cache store
> * The backend cluster is the cache store for the app server's cache
> It would be nice if the backend cache could inform the app server's cache about cache entry invalidations.
> This could be used when you want to use Infinispan clusters in your "branch offices" and have a "central" Infinispan clusters that receives all data updates and informs the "branch" clusters just about invalidations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira