Replies: 1 comment
-
I noticed that writes are slowish because it will hit the other nodes for a quorum. so basically a transaction is hitting 3 servers typically. If we relax linearizability for eventual ( aka CAP theory ) then we could put the change into NATS on the server it happened, and rely on it eventually doing the write on the other servers ? I guess though it relies on perfect ordering which is not possible for multi master unless we reinvent atomic clocks :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
https://github.com/k3s-io/kine now has NATS based storage.
Kind of useful for rqlite and similar systems.
I am totally biased as i use nats jetstream for its RAFT aspects and all the other goodies.
Beta Was this translation helpful? Give feedback.
All reactions