Home / Companies / AuthZed / Blog / Post Details
Content Deep Dive

CockroachDB 23.1 new defaults impact SpiceDB

Blog post from AuthZed

Post Details
Company
Date Published
Author
Jimmy Zelinskie
Word Count
887
Company Posts That Month
3
Language
English
Hacker News Points
-
Post removed?
No
Summary

SpiceDB is a unique database that implements a pattern called MVCC (Multi-Version Concurrency Control), which allows it to run queries against snapshots of the data instead of the actual data. This provides flexibility in terms of consistency levels, with options such as `at_exact_snapshot` allowing users to specify their desired level of consistency on each request. However, this also means that SpiceDB stores multiple versions of data, and requires a mechanism for garbage collection to manage these versions. In CockroachDB v23.1, the default configuration for `gc.ttlseconds`, which controls how long values are retained before being overwritten, has been changed from 25 hours to 4 hours, affecting SpiceDB users who rely on this feature. This change means that SpiceDB's --datastore-gc-window cannot be older than CockroachDB's gc.ttlseconds, limiting the range of times that can be queried in SpiceDB. For open-source users of SpiceDB, future versions will non-fatally warn and fallback to the CockroachDB value in this scenario to avoid downtime while upgrading.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Serverless 4 537 125 66 +32%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.