Repository navigation
Push Refresh : Allow users to update sync token from change events #230
Description
For the push refresh scenario, users can subscribe to key-value change events and invoke SetDirty method to ensure that the next call to RefreshAsync retrieves the updated configuration. This item tracks the addition of a way that allows users to provide the sync token received in the key-value change event, and ensures that the next refresh uses that token to receive the most-recent configuration, and avoids consistency issues due to replocation lag.
Activity
zhenlan commentedon Feb 4, 2021
We probably should just pass the event to
SetDirtyand then let the sync token flow transparently toRefreshAsync, so users don't need to know about the sync token.[-]Push Refresh : Add an API to allow users to update sync token from key-value change events[/-][+]Push Refresh : Allow users to update sync token from key-value change events[/+][-]Push Refresh : Allow users to update sync token from key-value change events[/-][+]Push Refresh : Allow users to update sync token from change events[/+]abhilasharora commentedon Feb 4, 2021
Yes, that's the plan. I updated the title to clarify that we want to allow users to pass sync token, and don't need an additional API. Here's the change to the
SetDirtymethod signature. We could also add multiple overloads, if needed.zhenlan commentedon Feb 4, 2021
Sounds good. Is it possible for the user to avoid parsing the sync token from the event?
abhilasharora commentedon Feb 4, 2021
When using the Service Bus SDK to receive events, the user code would need to perform three steps. I don't see a clean way to avoid these steps in user code in a generic way.
bye[] message.Bodyto a stringdata->syncTokensyncTokentoSetDirtymethodzhenlan commentedon Feb 4, 2021
Yes, I understand users normally don't deal with events from the Event Grid directly. It really depends on which handler service they choose. Maybe we can take the whole JSON string or the
dataportion as the parameter.I almost feel the sync token should be a required parameter. Without it, it relies on luck for the next refresh to fetch the latest change.
abhilasharora commentedon Feb 4, 2021
Yes, we could take the whole JSON string as a parameter, assuming it conforms to our event schema across all handlers. When using Event Grid and Service Bus, here's an example of what sample code could look like.
By default, we do have a randomized delay of up to 30 seconds before the
SetDirtycall would come into effect, which lowers the probability of missing the changes on next refresh. I do agree that making the sync token mandatory would help here, though it limits the use ofSetDirtyonly to scenarios that respond to change events.