ScyllaDB 1.7 introduces experimental support for counters

ScyllaDB 1.7 introduces experimental support for counters, a special type of column designed for efficient counting operations with atomic updates, compatible with Cassandra 2.1 or later. Counters only allow incrementing, decrementing, reading, or deleting their values and have unique limitations, such as not being able to be set to a specific value once deleted and not being used in primary keys. Implemented using state-based conflict-free replicated data types (CRDT), counters enable local atomic operations without node synchronization, though initial updates remain non-idempotent, preventing safe client retries in case of failure. The internal mechanism involves counter shards, owned by specific nodes, and synchronized through a leader-based update process that minimizes the need for complex consensus protocols. During reads, counter values are aggregated from all counter shards, and standard eventual consistency limitations apply. ScyllaDB plans a more efficient counter implementation in its upcoming release 1.8, which is expected to resolve current inefficiencies.

No tracked trend matches for this post yet.

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.