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
Broadcasts are all treated the same in Corrosion right now. However, nodes will broadcast their local changes to neighboring nodes immediately instead of randomly and eventually.
A concept of "priority" could be added for broadcasts to neighboring nodes.
When a node receives a priority broadcast, it should apply it immediately instead of queueing it to later batch insert it with other changes.
This is useful for faster eventual consistency "where it matters". It's likely a client interacting with a Corrosion node will be affecting data required on another node in close proximity.
The text was updated successfully, but these errors were encountered:
Broadcasts are all treated the same in Corrosion right now. However, nodes will broadcast their local changes to neighboring nodes immediately instead of randomly and eventually.
A concept of "priority" could be added for broadcasts to neighboring nodes.
When a node receives a priority broadcast, it should apply it immediately instead of queueing it to later batch insert it with other changes.
This is useful for faster eventual consistency "where it matters". It's likely a client interacting with a Corrosion node will be affecting data required on another node in close proximity.
The text was updated successfully, but these errors were encountered: