Infinispan Concepts: Difference between revisions
| Line 7: | Line 7: | ||
A ''cache container'' is the runtime structure that instantiates and manages one or more caches. In case of clustered caches, the cache container encapsulates the networking mechanisms required to maintain state across more than one JVM for its caches, including a JGroups stack. | A ''cache container'' is the runtime structure that instantiates and manages one or more caches. In case of clustered caches, the cache container encapsulates the networking mechanisms required to maintain state across more than one JVM for its caches, including a JGroups stack. | ||
Each cache container declares a set of caches that share a global configuration, so caches belonging to different containers can have different transport configurations, optimized for different use cases. | Each cache container declares a set of caches that share a global configuration, so caches belonging to different cache containers can have different transport configurations, optimized for different use cases. | ||
The cache container implementations are heavyweight objects. There should be possible to use just one cache container per JVM, unless specific configuration requires the availability of more than one instance - but in this case there will be a minimal and finite number of such instances. | The cache container implementations are heavyweight objects. There should be possible to use just one cache container per JVM, unless specific configuration requires the availability of more than one instance - but in this case there will be a minimal and finite number of such instances. | ||
Revision as of 15:48, 31 May 2016
Internal
Cache Container
A cache container is the runtime structure that instantiates and manages one or more caches. In case of clustered caches, the cache container encapsulates the networking mechanisms required to maintain state across more than one JVM for its caches, including a JGroups stack.
Each cache container declares a set of caches that share a global configuration, so caches belonging to different cache containers can have different transport configurations, optimized for different use cases.
The cache container implementations are heavyweight objects. There should be possible to use just one cache container per JVM, unless specific configuration requires the availability of more than one instance - but in this case there will be a minimal and finite number of such instances.
A WildFly cache container is the WildFly service wrapper around an Infinispan cache container. Each <cache-container> element eventually results in a org.infinispan.manager.DefaultCacheManager instance being created in the JVM.
The corresponding WildFly/JDG configuration element is <cache-container>. The <cache-container> elements are children of the "infinispan" (for WildFly) or "infinispan:server:core:" (for JDG) subsystems. More details about cache container configuration can be found here:
From an API perspective, the cache container is the primary API mechanism to retrieve cache instances or create cache instances on demand.
Cache Manager
A cache manager and a cache container represent similar concepts.
Cache
Connecting to an Infinispan Server
HotRot
The HotRod connector is configured in the infinispan:server:endpoint Section.
memcached
The memcached connector is configured in the infinispan:server:endpoint Section.
REST
The REST connector is configured in the infinispan:server:endpoint Section.