Re:Consistency Without Clocks: FaunaDB's Distributed Transac...
by jamesblonde on Friday October 19, 2018 @02:46PM
(#18258979)
I should add that it is not correct to say 'our throughput is constrained not by our consensus protocol'. A trivial example would be a workload of transactions, where each transaction has at least two non-conflicting writes on different partitions. FaunaDB will serialize those transactions, and you will bottleneck on the consensus protocol - compared to NDB.
[ Parent
| on HN ]
Re:Consistency Without Clocks: FaunaDB's Distributed Transac...
by ummonk on Sunday October 21, 2018 @12:51PM
(#18268849)
What he's saying is that the throughput number they mention is constrained by transaction conflicts. The limit for non-conflicting transactions allowed by the consensus protocol is no doubt much higher.