Verification suites built with Jepsen Lite, one per data store.
| store | what it covers |
|---|---|
sqlite/ |
SQLite, in-process and as a process killed with SIGKILL |
Each store gets a directory of its own, with its own deps.edn, its own src/
and its own README. They share nothing but Jepsen Lite: a store's driver
depends on that store and on nothing else, and its verification runs are its
own business. Adding one means adding a directory, not touching an existing
suite.
The shape they follow, and the reason for it, is Jepsen Lite's own: the
protocol a store is reached by and the way it is deployed are separate
axes, and the workloads, checkers and verdicts are identical across both. So a
suite is one set of operations plus one adapter per protocol, and an embedded
store needs a small driver process before anything can kill -9 it at all --
test code belonging to that store's suite, and described in its own README.
Run a suite from its own directory:
cd sqlite && clojure -M:jepsen