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

[Dan Berindei (JIRA)]

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

Dan Berindei updated ISPN-5012:
-------------------------------
    Fix Version/s: 7.2.0.Beta2
                       (was: 7.2.0.Beta1)


> 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
>             Fix For: 7.2.0.Beta2
>
>
> 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.3.11#6341)