I&#x27;m actually going to be discussing this at Strangeloop next month.<p><a href="http:&#x2F;&#x2F;www.thestrangeloop.com&#x2F;2015&#x2F;all-in-with-determinism-for-performance-and-testing-in-distributed-systems.html" rel="nofollow">http:&#x2F;&#x2F;www.thestrangeloop.com&#x2F;2015&#x2F;all-in-with-determinism-f...</a><p>VoltDB is actually a bit simpler with what it promises, full serializable ACID for all transactions. This is much easier to understand and verify than lesser isolation.<p>We think what we&#x27;ve done is pretty clever too. We&#x27;ve built a determinism checker into our replication engine, so that we can verify that each replica has the same state at each logical point in time, and each operation makes identical changes to that state.<p>Then we built test patterns that are designed to be as co-dependent as possible and run them against a replicated VoltDB cluster. That VoltDB cluster goes though one or more kinds of failure, including multiple simultaneous failure, and then a checker ensures no data is ever lost, corrupted or run in the wrong order.<p>It&#x27;s different from the FDB thing. The simulation they did is certainly easier to run on a pure KV store, but keep in mind we also have to test SQL that queries millions of rows, along with upserts, materialized aggregations, etc...<p>We&#x27;re working on some blog content on this in addition to my talk. Stay tuned.