exqlite
chiselstore
| exqlite | chiselstore | |
|---|---|---|
| 2 | 4 | |
| 197 | 563 | |
| 1.0% | 0.0% | |
| 7.9 | 0.0 | |
| 9 days ago | over 1 year ago | |
| C | Rust | |
| MIT License | MIT License |
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.
exqlite
-
Fly.io Buys Litestream
> Is support for SQLite in the Elixir ecosystem, particularly Ecto, good enough for this?
Why yes it is. I maintain the `exqlite` and `ecto_sqlite3` libraries and it was just integrated in with `kino_db` which is used by `livebook`.
https://github.com/elixir-sqlite/exqlite
-
Looking for an Open Source project to join part time
Could always use some help with progressing the sqlite ecto adapter I've been working on. https://github.com/warmwaffles/exqlite
chiselstore
-
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?
Absinthe Graphql - The GraphQL toolkit for Elixir
rqlite - The lightweight, distributed relational database built on SQLite.
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
sqlite_fdw - SQLite Foreign Data Wrapper for PostgreSQL
actordb - ActorDB distributed SQL database
risingwave - Cloud-native SQL stream processing, analytics, and management. KsqlDB and Apache Flink alternative. 🚀 10x more productive. 🚀 10x more cost-efficient.
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
dogehouse - Taking voice conversations to the moon 🚀
incubator-horaedb - HoraeDB is a high-performance, distributed, cloud native time-series database.
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB