Invalidating query cache entries replication
Global configuration defines global settings shared among all cache instances created by a single Embedded Cache Manager.
Shared resources like thread pools, serialization/marshalling settings, transport and network settings, JMX domains are all part of global configuration.
Programmatic Infinispan configuration is centered around the Cache Manager and Configuration Builder API.
Although every single aspect of Infinispan configuration could be set programmatically, the most usual approach is to create a starting point in a form of XML configuration file and then in runtime, if needed, programmatically tune a specific configuration to suit the use case best.
For example, you can read static XML configuration files and at runtime programmatically tune that same configuration.
Or you can use a certain static configuration defined in XML as a starting point or template for defining additional configurations in runtime.
The configuration file listed below provides sensible defaults and is perfectly valid.
A simple XML configuration file containing nothing more than a single infinispan element is enough to get you started.
If you want to be able to scale your caching layer independently from your application, or you need to make your data available to different applications, possibly even using different languages / platforms, use Infinispan Server and its various clients.
Data you place in Infinispan doesn’t have to be temporary: use Infinispan as your primary store and use its powerful features such as transactions, notifications, queries, distributed execution, distributed streams, analytics to process data quickly.
So, how can new configurations be defined based on other defined caches?
Take the previous example and imagine that instead of taking the default cache as base, a named cache called "replicated Cache" is used as base.