| ▲ | Consistency over Availability: How rqlite Handles the CAP theorem(philipotoole.com) | ||||||||||||||||
| 53 points by otoolep 7 days ago | 5 comments | |||||||||||||||||
| ▲ | nchmy 4 days ago | parent | next [-] | ||||||||||||||||
I wonder if there could be something between None and Weak... Don't check if it's the leader, but rather check (ideally locally, via some sort of flag that is updated on writes - when it's going to be communicating with the cluster anyway) if it's still part of the cluster/quorum. If so, then read locally. If not... reject the request since it might be stale? The idea is that it is stronger than None, but weaker than doing reads (or any communication at all at read-time) from the Leader. | |||||||||||||||||
| |||||||||||||||||
| ▲ | rvcdbn 4 days ago | parent | prev [-] | ||||||||||||||||
I'm sure there's a reason but I would expect a system like this to use leader leases for local reads | |||||||||||||||||
| |||||||||||||||||