case studies
A customer calls support. Their credit limit was 100 yesterday and it’s 50 today, and nobody told them why. The support agent can see the 50. Everything else is …
case studies
Prices change together. A new quarter’s price list touches every plan at once, and a half-applied list is worse than an old one: for a few minutes Pro might cost …
case studies
At two in the morning an alert fires: the orders database is answering slowly, and order requests are timing out. The on-call engineer raises the database timeout from 5 …
case studies
An operations agent watches the product catalog. Its metrics show 4.1% of reads returning stale data, above the 2% target, so it shortens the catalog cache’s …
testing
A store that keeps the reason behind every value is only useful if it keeps the value too. So before 0.1.0 went out, each promise XKV makes got a test aimed straight at …
explainer
The values that cause the most trouble are small. A credit limit. A timeout. A price. A flag that switches a feature on for ten percent of users. Each one fits in a few …
about
XKV stands for explainable key-value. KV is the usual shorthand for a key-value store, the simplest kind of database there is: you put a value under a key and get it back …
release
XKV 0.1.0 is out. It’s a small key-value store for Go that keeps one thing other stores throw away: the reason. Every write records who made it, why, and which …