4 ms·
Right. Talking about "Calvin", he says: > Nonetheless, it was able to bring the processing of that transaction to completion without having to abort it. It acc
by orangepenguin 8y ago
Right. Talking about "Calvin", he says:
> Nonetheless, it was able to bring the processing of that transaction to completion without having to abort it. It accomplished this via restarting the transaction from the same original input.
I may be misunderstanding, but if you have transactions recorded in such a way that any worker can replay from any point in time and reach the correct database state, then the transaction log must absorb all of the complexity. The problem has moved, but not changed.
- freels 8y agoThe big difference is that it's a much easier problem to solve in the context of a log (see Paxos, Raft, ZAB, et al), where the consensus membership is more or less fixed, as opposed to having to manage it among an adhoc membership set.