OpenHub framework uses Spring cache abstraction layer or Spring Boot (auto-configuration) for decoupling from specific cache implementation. Then it's possible to use different cache providers (such as Redis, ehCache, ...) without making changes in the code (only configuration).

Nevertheless there are implementations which use directly Hazelcast's features, for example org.openhubframework.openhub.core.throttling.ThrottleCounterHazelcastImpl for throttling counting.

By default, hazelcast is configured as standalone single-node. For cluster deployment it should be configured accordingly, see hazelcast specification for more info: (Hazelcast configuration, Cluster - Discovery Mechanisms).

# the location of the configuration file to use to initialize Hazelcast.
# the default Hazelcast configuration
spring.hazelcast.config=classpath:/config/ohf_hazelcast.xml

Spring Boot supports Hazelcast in two ways:

• direct Hazelcast support for solution itself
• Hazelcast as cache provider that is supported by caching Spring support

Both ways have different configuration Spring Boot parameters:  spring.hazelcast.config (has higher priority) vs spring.cache.hazelcast.config

@Bean
public Config hazelCastConfig() {
    Config config = new Config();
	config.set...

    return config;
}

@Bean
public CacheManagerCustomizer hazelCastCacheManagerCustomizer() {
    return new CacheManagerCustomizer<HazelcastCacheManager>() {
        @Override
        public void customize(HazelcastCacheManager cacheManager) {
            ...
        }
    };
}

There is the full example of Hazelcast configuration with detailed description of all configuration parameters.

There is org.openhubframework.openhub.core.config.CacheNames class with all defines cache names.