Currently, after performing an upsert, we inform the subscribed services of the new data in the Dynamic Content Configuration Service (DCCS), formerly known as config-manager, by publishing only the config IDs. This means that the services must query for the payload using the config IDs instead of receiving the payload directly through Redis notification.
@stefanciprian
The question is whether it would be more sensible for Redis to emit the entire payload, instead of the config IDs?
Currently, after performing an upsert, we inform the subscribed services of the new data in the Dynamic Content Configuration Service (DCCS), formerly known as config-manager, by publishing only the config IDs. This means that the services must query for the payload using the config IDs instead of receiving the payload directly through Redis notification.
@stefanciprian