HAhantusk·May 10, 2022
Same pattern is ActorDB: https://github.com/biokoda/actordb
In I'm all-in on server-side SQLitebiokoda
actordb
Erlang2014–2022
biokoda / actordb
actordb
ActorDB distributed SQL database
7Distinct people
10Mentions
0Explicit recommenders
1.9KGitHub stars
What to know before exploring
What it is
ActorDB distributed SQL database
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year10 dated mentions
Observed mentions: 2014-01-21 20:46:35 UTC to 2022-05-10 07:00:36 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 4 | 3 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
10 sourcesThe formalization of this approach is https://github.com/biokoda/actordb — which is essentially a sharded document store where one type of “document” is an SQL-addressable SQLite database.
Sadly, ActorDB seems to be inactive as a project—but the fundamental premise is sound.
I’d love to see the concept reimplemented as e.g. a Redis module (since a Redis cluster essentially has the same “shape” as ActorDB’s custom distributed K-V store.)
In 35% Faster Than The Filesystem (2017)ActorDB – Distributed SQL database
284 points · Open discussionNot to be confused with ActorDB, a distributed SQLite-based database for highly-sharded data. These two systems are similar in that they are both new SQL systems on top of SQLite, but they seem to differ greatly in use-case
https://github.com/biokoda/actordb
In Show HN: Rqlite v4.0 – With node-to-node encryptionActorDB distributed SQL database
3 points · Open discussionActorDB distributed SQL database
2 points · Open discussionActorDB distributed SQL database
3 points · Open discussionActorDB takes this about 100 steps further. It replicates the actual WAL pages instead of SQL commands. So the leader executes the SQL, followers just write the pages from leader.
https://github.com/biokoda/actordb
It uses LMDB to store everything instead of storing raft log in one place and SQLite in another. It can run thousands of SQLite instances at the same time and it actually compresses the pages when storing to LMDB.
You can query it with a MySQL client library (though Thrift is recommended). You can have multiple raft clusters, there is a complementary actordb_console app to manage it easily, it supports distributed transactions and more.
In Rqlite: Replicated SQLite using the Raft consensus protocolActorDB takes this concept much further. It replicates the WAL file (not sql statements).
http://www.actordb.com
https://github.com/biokoda/actordb
In Replicating SQLite using Raft ConsensusActorDB 0.5 released - a distributed SQL database
3 points · Open discussion