Analyses

jepsen.io · 259 words · saved by 2 readers

Since 2013, Jepsen has analyzed over two dozen databases, coordination services, and queues—and we’ve found replica divergence, data loss, stale reads, read skew, lock conflicts, and much more. Here’s every analysis we’ve published. Would you like Jepsen to analyze your distributed system? Contact aphyr@jepsen.io for pricing. Analyses generally take one to four months, depending on scope, and are bound by our research ethics policy. We work with your team to understand the system’s guarantees, design a test for the properties you care about, and build a reproducible test harness. We then help you understand what any observed consistency anomalies mean, and work with your engineers to file bugs and develop fixes. Jepsen can also provide assistance with your existing Jepsen tests—developing new features, performance improvements, visualizations, and more. Jepsen occupies a particular niche of the correctness testing landscape. We emphasize: Opaque-box systems testing: we evaluate real bi

Since 2013, Jepsen has analyzed over two dozen databases, coordination services, and queues—and we’ve found replica divergence, data loss, stale reads, read skew, lock conflicts, and much more. Here’s every analysis we’ve published. Aerospike2015-05-043.5.4 2018-03-073.99.0.3 Amazon RDS for PostgreSQL2025-04-2917.4 Bufstream2024-11-120.1.0 Capela2025-08-07dda5892 Cassandra2013-09-242.0.0 Chronos2015-08-102.4.0 CockroachDB2017-02-16beta-20160829 Crate2016-06-280.54.9 Datomic2024-05-151.0.7075 Dgraph2018-08-231.0.2 2020-04-301.1.1 Elasticsearch2014-06-151.1.0 2015-04-271.5.0…

Analyses

saved by

related reading