-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistency Violation #21
Comments
That's hypothetically possible, yeah. Good point :) Although in practice there are a bunch of defenses against it to the point where I think it's incredibly unlikely it'd ever be hit:
But it wouldn't be hard to grab the timestamp off the last message when we load the most recent messages from storage, so we should probably just do that given that it's effectively free. Thanks for checking out the example and mentioning this! |
Yeah, could even be a good example of using |
Clever, but I believe the durable object still runs into a consistency violation if the clock does go backwards because the object does not persist
lastTimeStamp
I could be wrong though, distributed systems are hard 🤯🤓
workers-chat-demo/src/chat.mjs
Lines 367 to 371 in 7e2972c
The text was updated successfully, but these errors were encountered: