biokoda/actordb

Health v2 · maintenance only

Flags: no_releases

Adoption not part of the score

1888 stars · 71 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

service · maturity maintenance

database database-driver rpc databases microservices backend developer-tools self-hosted distributed-sql sharding raft-consensus sqlite lmdb mysql-protocol erlang actor-model acid linux macos web-server

Member repositories

For agents

markdown · JSON · MCP: product_card(name="biokoda/actordb")