redix
ld
Our great sponsors
| redix | ld | |
|---|---|---|
| 3 | 6 | |
| 1,196 | 20 | |
| - | - | |
| 0.0 | 0.0 | |
| about 1 year ago | over 1 year ago | |
| Go | Go | |
| Apache License 2.0 | The Unlicense |
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.
redix
- Redcon - Redis compatible server framework for Rust
- A redis server that uses Postgres as its storage engine (redix v5)
-
A dead simple Key-value Storage API
I don’t get the idea of your module layout: nested vs unnested packages, lowercase vs uppercase vs capitalized directory names. Check out https://github.com/alash3al/redix to get an idea about clean module design.
ld
-
Using a httputil reverse proxy to host gRPC REST & static web content (eg HTML) on a single port
I slammed together a database based on this wire protocol feature: MikkelHJuul/ld the database serve bytes, the client can deserialize those by replacing the bytes with a message (in the proto-file)
-
A dead simple Key-value Storage API
Hell, I even built a kv-database myself that I just announced some weeks ago, based on badgerDB: ld. It's API is the api I would say qualifies as a simple actual kv database api. KeyRange { String prefix, from, to, pattern (pattern may be a bit over the top) } The database is value agnostic
-
Protobuf Database: ld & ld-client: interactive client
[ld:0.1.3](https://github.com/MikkelHJuul/ld) is out
-
ld - 0.1.1: protocol buffers database
Just after pushing 'Post'; I thought to my self: I haven't done nearly enough testing! This is release [0.1.1](https://github.com/MikkelHJuul/ld/pull/2) focusing on testing, I fixed some bugfixes with the `Iterator` in `impl/iterator.go`, but mostly I added 50-some tests spanning 900 lines of test code.
-
Protocol buffers database, a Key-Value database on the wire
I got my database into a release candidate: ld - a protocol buffers database
-
gRPC bytes
The obvious use case is the one of a key value database: I have an older personal project I wanted to do this for, ld (yes I know there is a c linker called ld) basically the client implements their proto file saving whatever they wanted at a given key and the database never touch the bytes, it servers back those bytes which should be re-serialisable to the same object. (The project is semi abandoned, I hope to use badger or boltdb to implement it some time)
What are some alternatives?
exts - Elixir Terms Storage, ets wrapper.
protoc-gen-star - protoc plugin library for efficient proto-based code generation
IceFireDB - @IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.
social - social network in GRPC, Go, mysql, and vuejs,
rethinkdb - Rethinkdb client in pure elixir (JSON protocol)
sled - the champagne of beta embedded databases
Jet - A key-value db api with multiple storage engines and key generation
ntru_elixir - a NIF for libntru. NTRU is a post quantum cryptography algorithm.
s2geometry - Computational geometry and spatial indexing on the sphere
upper.io/db - Data access layer for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.
S2 geometry - S2 geometry library in Go