I&#x27;d like to know more about read performance. My understanding is that when you base your system on Raft, you have to choose one of two operating modes:<p>- all reads go through the Raft state machine, which means that reading from one node implies talking to at least a quorum of nodes. Consul is an example of this behavior. It provides strong consistency but reduces the performance gain from horizontal scaling. (for Consul at least it&#x27;s been shown that heavy read loads can cause leadership transitions as the master gets overwhelmed).<p>- Reads are processed by the local node only. This is fast and scalable but is basically &quot;eventual consistency&quot;. A read immediately following a write is not guaranteed to see the write. etcd works this way by default (unless you pass ?quorum=true to your read request)<p>How does Kudu behave (or, rather, how is it <i>intended</i> to behave)?