Re:FoundationDB 6.0 released, featuring multi-region support
by ryanworl on Monday November 19, 2018 @07:17PM
(#18490895)
There are two reasons for this I can see:
1) All mutations and key ranges are stored locally and submitted when the transaction commits. Lots of data to transfer.
2) the optimistic conflict checker can process one range (even if it is a lot of underlying keys) a lot easier than each individual key in that range
Yes, the 5 second limit could be a problem.