Distributed cache updating algorithm for the dynamic source routing protocol
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.The configuration file listed below provides sensible defaults and is perfectly valid.However, that would only give you the most basic, local mode, non-clustered cache manager with no caches.
A simple XML configuration file containing nothing more than a single infinispan element is enough to get you started.
In fact, declarative configuration, behind the scenes, invokes the programmatic configuration API as the XML configuration file is being processed.
One can even use a combination of these approaches.
Once constructed, Cache Managers should be made available to any component that require to interact with it via some form of application-wide scope such as JNDI, a Servlet Context or via some other mechanism such as an Io C container.
Every aspect of Infinispan that can be configured declaratively can also be configured programmatically.