Kinf of. But it's not really Consistent in the CAP sense, as it only provides snapshot isolation, not linearizability, plus the A in CAP is kind of useless. (CA

Kinf of. But it's not really Consistent in the CAP sense, as it only provides snapshot isolation, not linearizability, plus the A in CAP is kind of useless. (CAP is an amazing theoretical milestone nonetheless, just too narrow for real life situations. Basically it's a simple no-go theorem.) In practice even this ToyDB is likely able to serve requests in a degraded state (probably as long as the Raft leader's timer does not expire, and if there's a quorum of nodes they can reelect a leader). And it seems that if a node falls out of sync it will automatically rejoin and try to replay the logs. (As long as they are available of course.) https://github.com/erikgrinaker/toydb/blob/master/docs/architecture.md#raft-tradeoffs https://github.com/erikgrinaker/toydb/blob/master/docs/archi... https://www.youtube.com/watch?v=hUd_9FENShA https://www.youtube.com/watch?v=hUd_9FENShA https://blog.acolyer.org/2014/11/07/highly-available-transactions-virtues-and-limitations/ https://blog.acolyer.org/2014/11/07/highly-available-transac...