2.14: streaming responses, and a breaking change
Responses can now stream. The v1 batch endpoint is removed, six months after deprecation. Upgrade notes inside...
What changed in Digest, and why. Every version, every incident, and the engineering behind them.
Responses can now stream. The v1 batch endpoint is removed, six months after deprecation. Upgrade notes inside...
Every schema change runs against a copy of production, twice, before it touches production once. The pipeline, in detail...
Every request has a trace. Here is how to find it, what each span means, and how to tell our latency from yours...
Every response now says how much of your limit is left and when it resets. The dashboard shows the same, per key...
On 14 August, reads returned stale data for forty-one minutes. What happened, what we did, and what changes...
digest diff shows what an apply would change, before it changes it. Also: config validation, and a faster login...
Rotate an API key without a second of failed requests, using overlapping keys and the grace period...
Every error Digest returns carries a stable code. What the codes are for, and how we stop them changing...
Export any query to CSV, JSON or Parquet. Runs in the background, notifies when done, and keeps the file for seven days...
A configuration change took the API down for six minutes on 3 July. Short account, and why we now deploy on Fridays anyway...
Failed deliveries retry with exponential backoff for 24 hours. The delivery log shows every attempt...
Three years on a message broker, one month on a table in the database. What we gained, what we gave up, and the numbers...
Loading...