-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
nats-io/nats-architecture-and-design
#358Labels
2.12+Features for 2.12 and beyondFeatures for 2.12 and beyondacceptedThe defect or proposal as been acceptedThe defect or proposal as been acceptedneeds designNeeds design or ADRNeeds design or ADRneeds infoAdditional info is neededAdditional info is neededproposalEnhancement idea or proposalEnhancement idea or proposal
Description
Proposed change
Since introducing Direct Get we lost our, admittedly imperfect, read-after-write consistency in KV stores.
We felt then that was an acceptable behaviour change but its clear that there are significant need for control in this area.
We might still default to the current behaviour but should at least provide a opt-in to be in-cluster consistent and in-supercluster eventually consistent.
This can take a few forms:
- We can add a leader-only direct get subject
- We can adopt some of the thoughts @MauriceVanVeen has around improving the consistency of the raft layer
Even if we do nothing, we should very clearly and prominently document what we do and do not support in places other than the ADR.
Use case
Increase the areas KV is applicable
Contribution
No response
Metadata
Metadata
Assignees
Labels
2.12+Features for 2.12 and beyondFeatures for 2.12 and beyondacceptedThe defect or proposal as been acceptedThe defect or proposal as been acceptedneeds designNeeds design or ADRNeeds design or ADRneeds infoAdditional info is neededAdditional info is neededproposalEnhancement idea or proposalEnhancement idea or proposal