In Infinispan 9.1 we introduce the clustered counters. It is a counter distributed and shared among all nodes in the cluster and today we are going to know more about it.
To use a counter in your Infinispan cluster, first you have to add the maven dependency to your project. As you can see, it is simple as doing:
After adding the module, you can retrieve the CounterManager and start creating and using counters.
Each CounterManager is associated to a CacheManager. But, before showing how to use it, first we have some configuration to be done.
There are two attributes that you can configure: The num-owner - that represents the number of copies of the counter’s value in a cluster; and the reliability - that represents the behavior of the counters in case of partitions.
Below, is the configuration example with their default values. XML:
Then, you can retrieve the CounterManager from the CacheManager, as shown below, and start using the counters!
A counter is identified by its name. Also, it is initialized with an initial value (by default 0) and it can be persisted, if the value needs to survive a cluster restart.
There are 2 types of counters: strong and weak counters.
The strong counter provides higher consistency. Its value is known during the update and its updates are applied atomically. This allows to set boundaries and provides conditional operation (as compare-and-set).
A strong counter can be configured in the configuration file or programatically. They can be also created dynamically at runtime. Below shows us how it can be done:
The strong counter fits the following uses cases:
Global Id Generator
Due to its strong consistency, it can be used as a global identifier generator, as in the example below:
If bounded, it can be used as a simple rate limiter. Just don’t forget to invoke reset()…
Simply count "stuff"
Well, it is a counter after all…
The weak counter provides eventual consistency and its value is not known during updates. It provides faster writes when comparing with the strong counter.
As in strong counter, the weak counter can be configure its name and its initial value. In addition, a concurrency-level can be configure to set the number of concurrent updates that can be handled in parallel. Below shows us how to configure it:
The main use case for the weak counter includes all scenarios where its value isn’t needed while updating the counter. For example, it can be used to count the number of visits to some resource: