actordb
ActorDB distributed SQL database (by biokoda)
chiselstore
SQLite + Little Raft = 🚀 (by chiselstrike)
actordb | chiselstore | |
---|---|---|
1 | 4 | |
1,883 | 563 | |
0.0% | 0.0% | |
10.0 | 0.0 | |
over 1 year ago | over 1 year ago | |
Erlang | Rust | |
Mozilla Public License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
actordb
Posts with mentions or reviews of actordb.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-09.
chiselstore
Posts with mentions or reviews of chiselstore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-04.
-
SQLite: QEMU All over Again?
it? What's the big deal about not fitting well with SQLx? This isn't a requirement for such a library to be successful. What other problems is it allegedly suffering from?
[1] https://github.com/chiselstrike/chiselstore
- Fly.io Buys Litestream
-
Distributed SQLite for Rust
I've looked at the https://github.com/chiselstrike/chiselstore/blob/main/proto/... - and calling the service "RPC" is not great if this is going to be bundled with other gRPC services - why not call it "chiselStore" or something more concrete?
on a 2nd note, each method should have it's own Request Response, and ideally they should be suffixed same way. Returning same proto for multiple methods might break future compatibility - e.g. what if AppendEntries needs to return somehing else than Void? - ideally you make it from the start to return an empty AppendEntriesResponse, and then you can extend that proto.
https://developers.google.com/protocol-buffers/docs/proto3#u...
What are some alternatives?
When comparing actordb and chiselstore you can also consider the following projects:
exqlite - An SQLite3 driver for Elixir
rqlite - The lightweight, distributed relational database built on SQLite.