redcon
redix
| redcon | redix | |
|---|---|---|
| 4 | 3 | |
| 2,097 | 1,196 | |
| - | - | |
| 0.0 | 0.0 | |
| 6 months ago | about 1 year ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
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.
redcon
-
Should I write my own Redis?
Hello,
there is an excellent library for golang which allows you to implement the redis server protocol: https://github.com/tidwall/redcon
I would like to put in the effort to implement most redis commands there and map them to SQL so that all data can be saved inside a fine tuned sqlite.
Essentially if this is implemented we would have a database compatible to redis, the difference is that data is saved to disk and not to RAM.
Is there a use case for that? Do people want that? There is some interesting things that could be done with that but I am not sure if the world needs this.
-
Redcon - Redis compatible server framework for Rust
I ported it from Go and use it for my Tile38 project.
- Redis-compatible key-value store in Go
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.
What are some alternatives?
rsync - gokrazy rsync
exts - Elixir Terms Storage, ets wrapper.
Tile38 - Real-time Geospatial and Geofencing
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.
rosedb - Lightweight, fast and reliable key/value storage engine based on Bitcask.
rethinkdb - Rethinkdb client in pure elixir (JSON protocol)
jupiter - Jupiter is a framework for wrapping compute or memory intense components to provide them as high throughput and ultra low latency services to applications using the Redis RESP protocol
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.
redcon.rs - Redis compatible server framework for Rust
upper.io/db - Data access layer for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.