REQUIRED BACKGROUND: boost-start, boost-wrapper-config. Layout/trio convention → boost-maintainer.

import buntdb "github.com/xgodev/boost/factory/contrib/tidwall/buntdb/v1"

db, err := buntdb.NewDB(ctx)
if err != nil { log.Fatalf("buntdb: %v", err) }
defer db.Close()

Configure path, sync mode, auto-shrink under boost.factory.buntdb.* (override BOOST_FACTORY_BUNTDB_*). Use :memory: for pure in-memory.

When to reach for buntdb

Local cache for derived data that's cheap to recompute on cold start.
Test/fixture KV that you don't want to spin up Redis for.
Sidecar state for a worker (rate limit counters, circuit-breaker state).

For shared state across replicas, don't use buntdb — it's per-process. Use boost-wrapper-cache with a Redis driver.

boost-factory-buntdb

When to reach for buntdb