Extensions Overview

Grove KV extensions are application-level primitives built entirely on the *kv.Store interface. Because they only use the standard Store operations (Get, Set, Delete, Expire, Exists), every extension works with any backend driver -- Redis, Memcached, DynamoDB, BoltDB, or Badger -- with zero driver-specific code.

What Are Extensions?01

Each extension is a standalone Go struct that wraps a *kv.Store and provides a focused, higher-level API for a common distributed-systems pattern. You create an extension by passing your existing store, and the extension handles key management, serialization, TTLs, and coordination logic internally.

import (
    "github.com/xraph/grove/kv"
    "github.com/xraph/grove/kv/plugins"
)

// Any Store, any driver.
store, _ := kv.Open(driver)

// Create extensions from the same store.
sessions := plugins.NewSessionStore(store)
limiter  := plugins.NewRateLimiter(store, "api", 100, time.Minute)
lock     := plugins.NewLock(store, "deploy", 10*time.Second)
counter  := plugins.NewAtomicCounter(store, "visitors")
board    := plugins.NewLeaderboard(store, "scores")
queue    := plugins.NewQueue(store, "tasks")

Driver-Agnostic by Design02

Extensions depend only on the *kv.Store interface, not on any specific driver. This means:

• Swap backends freely -- switch from BoltDB in development to Redis in production without touching extension code.

• Test with any driver -- use an in-memory Badger store in tests and a real Redis cluster in production.

• Compose with hooks -- all Store-level hooks (logging, namespacing, compression, encryption) apply transparently to extension operations.

Available Extensions03

Next Steps04