nebula-graph
rqlite
Our great sponsors
| nebula-graph | rqlite | |
|---|---|---|
| 3 | 112 | |
| 832 | 14,862 | |
| - | 1.3% | |
| 0.0 | 9.9 | |
| over 1 year ago | 6 days ago | |
| C++ | Go | |
| Apache License 2.0 | 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.
nebula-graph
- VSCode-nGQL, nGQL extension for VSCode
-
Developing a database in Go
That problem you faced is a reason why Graph databases were created. Take a look at NebulaGraph https://nebula-graph.io/ which has an SQL-like query syntax and already has all the features you mention in your list.
- Nebula Graph 2.0: A brand-new open-source distributed graph database
rqlite
- The lightweight, easy-to-use, distributed relational database built on SQLite
-
CursusDB – A new scalable distributed document oriented database
Seems like you could do the same with rqlite [1], since SQLite supports JSON.
[1]: https://rqlite.io
-
Rqlite 8.0
rqlite[1] creator here, happy to answer any questions about rqlite, this latest release, and how it works.
[1] https://rqlite.io
-
Adding new database engine support
I found simple distributed RQlite https://github.com/rqlite/rqlite based on raft and sqlite. How hard is to add it?
- I'm All-In on Server-Side SQLite
-
So, you want to deploy on the edge?
rqlite[1] creator here, happy to answer any questions. rqlite also supports read-only nodes, which can also help with reads at the "edge". It probably wouldn't scale to 100s of nodes, it is an option.
"rqlite supports adding read-only nodes. You can use this feature to add read scalability to the cluster if you need a high volume of reads, or want to distribute copies of the data nearer to clients – but don’t want those nodes counted towards the quorum. These types of nodes are also known as non-voting nodes."
[1] https://rqlite.io/
[2] https://rqlite.io/docs/clustering/read-only-nodes/
- LiteFS Cloud: Distributed SQLite with Managed Backups
- Show HN: Rqlite, distributed DB built on SQLite, now runs on MIPS, RISC, PowerPC
- rqlite v7.19.0: the lightweight distributed relational database built on Go, Raft, and SQLite -- now runs on MIPS, PowerPC, and RISC
- rqlite v7.18: the lightweight distributed database built on Go, Raft, and SQLite -- now with new Unified HTTP endpoint for easy reads and writes
What are some alternatives?
ArangoDB - 🥑 ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
Neo4j - Graphs for Everyone
litestream - Streaming replication for SQLite.
NebulaGraph Database - A distributed, fast open-source graph database featuring horizontal scalability and high availability
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
goostub - Porting bustub (https://github.com/cmu-db/bustub) in Go for fun (that's why I name it goostub)
bolt
chai - Modern embedded SQL database
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]
nebula-docker-compose - Docker compose for Nebula Graph
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.