What is an OfflineConfiguration?

While exploring the different builds and modules of the JuliGamesCore, you might have seen the so called “OfflineConfiguration” that seems to be part of the Configuration System.

First you need to know: You can use them to temporarily manage data in a Configuration (like defaults), but you need to understand that they are not connected to Hazelcast, they are not distributed, they are not managed and they are not represented by a file a user can edit.

What is the difference between the “CoreConfiguration” and the “OfflineConfiguration”? At first glance they are very similar, because they both implement the “Configuration” Interface that is part of the Configuration API. And both of them are using a Map to manage their data, but the Map that is used by the “CoreConfiguration” is backed by Hazelcast in form of a “Distributed Object”. That means, that all data that is managed by the “CoreConfiguration” is synced live and on-demand with all other Cores.

The OfflineConfiguration is backed by a normal “HashMap” and does not support live synchronized data distribution!