# zuoyebang/bitalostored

Bitalostored is a high-performance distributed storage system, core engine based on bitalosdb(self-developed), compatible with Redis protocol.

Repository: https://github.com/zuoyebang/bitalostored
Canonical: https://ross.abutalabs.com/products/bitalostored
Homepage: https://bitalos.zuoyebang.com
Language: Go
License: Apache-2.0
License Family: permissive
Topics: database, distributed-storage, high-performance, kvstore, nosql, redis, storage-engine, bitalosdb
Last push: 2026-04-03T02:54:24+00:00

## Health v2 (maintenance only)
Score: 70/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 75, release rhythm 65, longevity 65
- inputs: {"age_days": 919, "days_push": 152, "days_rel": 152, "gap_med": 57.0, "n_releases_24m": 5}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2167, forks 154 (observed 2026-08-28T04:06:21.406219+00:00)

## What it is
Bitalostored is a high-performance distributed KV storage system from Zuoyebang, built on its self-developed bitalosdb engine and compatible with the Redis protocol. It stores data on low-cost disks instead of memory, includes proxy and dashboard components, and supports sharding, Raft-based consistency, and multi-cloud disaster recovery.

## Use cases
- replace redis with a cheaper disk-based kv store
- run a redis-compatible database with horizontal scaling
- store large kv datasets without fitting in memory
- deploy a distributed cache with multi-cloud disaster recovery
- migrate redis workloads to lower-cost storage
- scale kv storage to hundreds of shards with fast expansion

## When to choose
- you need Redis protocol compatibility but want disk-based storage to cut memory costs
- you need a distributed, sharded KV store with Raft replication and disaster recovery
- you have very high QPS KV workloads and want proven production stability

## When to avoid
- you need full Redis feature coverage or advanced data structures beyond supported commands
- you want a small embedded or single-node library rather than a cluster service
- your dataset is small enough that plain Redis in memory is simpler and sufficient

## Facets
- artifact type: service
- maturity: stable
- function: database, caching, search-engine
- domain: databases, microservices, backend, self-hosted
- platform: go, self-hosted
- tags: redis-compatible, kv-store, storage-engine, distributed-storage, raft, sharding, nosql, linux, docker

## Member repositories
- zuoyebang/bitalostored (main) score 70

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:21.406219+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:49:55.912808+00:00, confidence not recorded.
  - readme: https://github.com/zuoyebang/bitalostored (fetched 2026-08-28T04:06:21.406219+00:00, sha 32f84d25a551)
  - homepage: https://bitalos.zuoyebang.com (fetched 2026-08-29T10:29:50.818391+00:00, sha 181490358d6c)
  - site_page: https://bitalos.zuoyebang.com/guide/01-intro (fetched 2026-08-29T10:29:50.820865+00:00, sha e4a514569574)
- Data as of 2026-08-30T08:39:29.467469+00:00.