[infinispan-issues] [JBoss JIRA] (ISPN-5012) ClusterRegistry as a service cache provider

Adrian Nistor (JIRA) issues at jboss.org
Mon Feb 1 11:57:00 EST 2016


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

Adrian Nistor resolved ISPN-5012.
---------------------------------
    Fix Version/s:     (was: 8.2.0.CR1)
       Resolution: Duplicate Issue


> ClusterRegistry as a service cache provider
> -------------------------------------------
>
>                 Key: ISPN-5012
>                 URL: https://issues.jboss.org/browse/ISPN-5012
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Core
>            Reporter: Tristan Tarrant
>            Assignee: Tristan Tarrant
>
> The ClusterRegistry is currently a volatile, replicated cache with a composite key and it does not serve the original purpose for which it was built. It should be refactored to be a service cache factory with a builder API based on desired features and a NamingStrategy so that we can have "well-known" caches as well as temporary caches. It should also be possible to use the cache dependency mechanism to "chain" service cache lifecycles to other caches.
> Here's an example API (not a real example):
> RegistryBuilder builder = registry.getBuilder();
> builder.persistent().clustered().dependsOn(Cache<?,?> cache).namingStrategy(new StaticCacheNamingStrategy("___protobuf_metadata"))
> This registry would be able to provide caches to the following use cases:
> - protobuf schemas
> - hotrod topology
> - security acl
> - map/reduce work caches
> - index caches
> - etc.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the infinispan-issues mailing list