Scylla
dqlite
| Scylla | dqlite | |
|---|---|---|
| 19 | 33 | |
| 12,772 | 3,741 | |
| 1.4% | 0.5% | |
| 10.0 | 9.4 | |
| about 6 hours ago | about 12 hours ago | |
| C++ | C | |
| GNU Affero General Public License v3.0 | GNU General Public License v3.0 or later |
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.
Scylla
- ScyllaDB: NoSQL data store using the seastar framework
-
Database 101: How to Model Leaderboards for 1M Player's Game.
Then I decided to talk to my boss and ask him if I could work with the YARG guys and the condition was to create something cool enough to implement ScyllaDB (NoSQL Wide-column Database) since I'm working as a Developer Advocate there. You won't believe how the simplicity and scalability brought by ScyllaDB perfectly fit the needs of YARG.in!
- Potential for silent data loss on ScyllaDB 5.2.x
-
Why ScyllaDB is Moving to a New Replication Algorithm: Tablets
ScyllaDB now has initial support for a new replication algorithm: tablets...
-
What are some C++ projects with high quality code that I can read through?
Scylla which is a C++ implementation of the Cassandra distributed K:V store https://github.com/scylladb/scylladb
-
Take Advantage of Git Rebase
What you say is impossible, we pretty successfully apply at ScyllaDB (see https://github.com/scylladb/scylladb/commits/master).
I'm not sure 100% of the commits compile & pass all tests - there may be some mistakes - but generally we're in a pretty good state, and the clean git log is being successfully used for bisecting.
If you want even larger scale - if I understand correctly, the Linux kernel practices a similar thing, which is where we got this practice from (ScyllaDB founders came from kernel development). And since Git was originally created to help developing Linux - that's where you want to look for good practices.
- Reducing logging cost by two orders of magnitude using CLP
- How Palo Alto Networks Replaced Kafka with ScyllaDB for Stream Processing
- Catch exceptions without even try-ing
-
Databases inside or outside k8s cluster?
Examples: - Vitess - MySQL cluster - YugabyteDB - ScyllaDB - Couchbase - ArangoDB
dqlite
-
Marmot: Multi-writer distributed SQLite based on NATS
If you're interested in this, here are some related projects that all take slightly different approaches:
- LiteSync directly competes with Marmot and supports DDL sync, but is closed source commercial (similar to SQLite EE): https://litesync.io
- dqlite is Canonical's distributed SQLite that depends on c-raft and kernel-level async I/O: https://dqlite.io
- cr-sqlite is a Rust-based loadable extension that adds CRDT changeset generation and reconciliation to SQLite: https://github.com/vlcn-io/cr-sqlite
Slightly related but not really (no multi writer, no C-level SQLite API or other restrictions):
- comdb2 (Bloombergs multi-homed RDMS using SQLite as the frontend)
- rqlite: RDMS with HTTP API and SQLite as the storage engine, used for replication and strong consistency (does not scale writes)
- litestream/LiteFS: disaster recovery replication
- liteserver: active read-only replication (predecessor of LiteSync)
- I'm All-In on Server-Side SQLite
-
SQLite performance tuning: concurrent reads, multiple GBs and 100k SELECTs/s
I'd be curious for a similar tuning with Dqlite: https://github.com/canonical/dqlite
- Strong Consistency with Raft and SQLite
-
9 years of open-source database development: reviewing the designs
Anyone knows how the DB this is about, https://rqlite.io/, compares with https://dqlite.io/ by Canonical (both seem to be distributed versions of sqlite)?
- SQLite the only database you will ever need in most cases
-
Transcending Posix: The End of an Era?
For folks' context, the new tool that's being discussed in the thread mentioned by the parent here is litefs [0], as well as which you can also look at rqlite [1] and dqlite [2], which all provide different trade-offs (e.g. rqlite is 'more strongly consistent' than litefs).
[0]: https://github.com/superfly/litefs
[1]: https://github.com/rqlite/rqlite
[2]: https://github.com/canonical/dqlite
-
SQLite is not a toy database
I presume you're familiar with https://github.com/canonical/dqlite (made by my employer) and https://github.com/rqlite/rqlite (unrelated)? How will mvsqlite compare to those?
-
GitDB, a distributed embeddable database on top of Git
Check out dqlite, it's sqlite but with a raft consensus to distribute changes through a log: https://dqlite.io/ You can link it in as a library too, it sounds like exactly what you want.
- Ask HN: Free and open source distributed database written in C++ or C
What are some alternatives?
Apache HBase - Apache HBase
rqlite - The lightweight, distributed relational database built on SQLite.
Druid - Apache Druid: a high performance real-time analytics database.
kine - Run Kubernetes on MySQL, Postgres, sqlite, dqlite, not etcd.
Apache Cassandra - Mirror of Apache Cassandra
litestream - Streaming replication for SQLite.
OpenTSDB - A scalable, distributed Time Series Database.
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
druid - A data-first Rust-native UI design toolkit.
boringproxy - Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.
scylla-operator - The Kubernetes Operator for ScyllaDB
Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication