Good idea. Also - beyond performing the necessary validations at bootstrap - I'd like to see the "hot path" of generating a new sequence number minimized to the smallest safe amount of code.

Essentially we might need a separate ClusteredCounterCommand for each sequence, and move most of the code in org.hibernate.ogm.datastore.infinispan.persistencestrategy.counter.ClusteredCounterCommand.nextValue(NextValueRequest) to its constructor.