3 ms·
From past experience in the database industry, command logs are insufficient at maintaining data integrity after a crash. They capture the bare minimum informat
by falcolas 11y ago
From past experience in the database industry, command logs are insufficient at maintaining data integrity after a crash. They capture the bare minimum information to reproduce a transaction, which is frequently not enough information. A log of "I'm changing field X from A to B" produces much more reliability in practice.
- jhugg 11y agoI think it really depends on the product. Determinism has been a big issue with logical logs in many systems, but it’s only a problem if you don’t plan and test for it. If you’re interested in how VoltDB ensures and tests determinism, check out my talk from StrangeLoop this year: https://www.youtube.com/watch?v=gJRj3vJL4wE https://www.youtube.com/watch?v=gJRj3vJL4wE
- MichaelGG 11y agoIf they are capturing enough to reproduce a transaction, then by definition that's enough information :). Non-deterministic commands (WHERE RANDOM() without a known seed) are the problem.\