You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to know if there is a way to guarantee exactly-once execution for commands. The situation I am in is pretty specific:
We are using Redis to cache some application data during user interactions. During those interactions values might change, this is when we update the values.
For some reason the connections gets dropped occasionally on write acknowledgement. This is when the command gets queued for re-execution, but before that an update due to user interactions is done. After the update the re-execution takes place, thus updating the value to the previous one.
What can I do to guarantee only the most recent value is the one persisted in Redis?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to know if there is a way to guarantee exactly-once execution for commands. The situation I am in is pretty specific:
What can I do to guarantee only the most recent value is the one persisted in Redis?
Beta Was this translation helpful? Give feedback.
All reactions