# biokoda/actordb

ActorDB distributed SQL database

Repository: https://github.com/biokoda/actordb
Canonical: https://ross.abutalabs.com/products/actordb
Language: Erlang
License: MPL-2.0
License Family: copyleft
Last push: 2022-11-10T05:09:21+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 4607, "days_push": 1392, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1888, forks 71 (observed 2026-08-28T04:05:49.300820+00:00)

## What it is
ActorDB is a distributed SQL database written in Erlang that combines the scalability of a KV store with full relational query capabilities by sharding data into per-actor SQLite databases replicated via Raft consensus. It exposes a MySQL-compatible protocol and Thrift interface, supports ACID transactions across actors, and runs on one or many servers with no single point of failure.

## Use cases
- store per-user relational data for a large app like a mail or file-sync service
- horizontally scale a SQL database without giving up ACID guarantees
- run a distributed database with explicit sharding by actor
- query across many sharded actors in a single transaction
- use a MySQL driver to connect to a distributed SQL backend
- partition a KV-style SQL table across all servers in a cluster

## When to choose
- your data model partitions naturally into per-entity (e.g. per-user) chunks
- you need consistent, ACID distributed SQL rather than eventual consistency
- you want horizontal scalability with no special client drivers
- you need online schema updates and node additions without downtime

## When to avoid
- you need heavy cross-actor joins or analytics over the whole dataset
- you require a mature ecosystem with active development and recent releases
- you need stored procedures or advanced features of PostgreSQL/MySQL
- your workload is a single small dataset where a plain RDBMS suffices

## Facets
- artifact type: service
- maturity: maintenance
- function: database, database-driver, rpc
- domain: databases, microservices, backend, developer-tools
- platform: self-hosted
- tags: distributed-sql, sharding, raft-consensus, sqlite, lmdb, mysql-protocol, erlang, actor-model, acid, linux, macos, web-server

## Member repositories
- biokoda/actordb (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:49.300820+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-30T03:13:29.392742+00:00, confidence not recorded.
  - readme: https://github.com/biokoda/actordb (fetched 2026-08-28T04:05:49.300820+00:00, sha a08c98846a6d)
- Data as of 2026-08-30T08:39:29.467469+00:00.