Settings are not synced between multiple Core instances when there is a change

[3keyroman]

The current caching mechanism of settings does not work across multiple instances of Core service.

The reason is that the cache is updated only for the instance through which the change in settings was requested.

The caching mechanism should be updated in a way that it will be applied to all instances consistently.
One of the suggested approach is to update cache regularly in defined time interval, for example 30 seconds.
Or update setting consistently for all Core services using push mechanism, where we can utilize also messaging.

The desired behaviour is that all running Core instances will have updated settings when there is a change.

The workaround is to restart Core deployment, and restarted instances will update the settings on startup, however, it is not practical to restart deployment every time there is a change in settings.