7 ms·
That is interesting -- using Coq to prove crash safety and consistency. It is a bit in the spirit of how Kyle (Aphyr)'s Knossos tool checks databases in his "Ca
by rdtsc 11y ago
That is interesting -- using Coq to prove crash safety and consistency. It is a bit in the spirit of how Kyle (Aphyr)'s Knossos tool checks databases in his "Call Me Maybe" series.
There should definitely be an equivalent thing for data corruption. There sure have databases and systems that made lofty marketing claims only to then silently corrupt user data (really, one of the most terrible things that could happen -- as it will corrupt your backups and might not be noticed for a while).
Also due to proliferation of VMs/containers. The model checker would have to include abnormal behaviors in both the host and the VM instance. Say pull the power on the host or VM.
Looking at products that store data I have both designed my own, so I know exactly how and when data checkpoints are happening or evaluated a few DBs. Or I like CouchDB for an off-the-shelf example. It has an append-only and crash-only design. Stopping can be done by kill -9 the process or backing can happen anytime, take EBS snapshots anytime. You'll pay for it perhaps in raw write performance but it has worked great for me.