IceFireDB
act
Our great sponsors
| IceFireDB | act | |
|---|---|---|
| 29 | 2 | |
| 1,075 | 188 | |
| 0.8% | 0.0% | |
| 9.3 | 3.9 | |
| 2 days ago | about 1 month ago | |
| Go | C | |
| MIT License | 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.
IceFireDB
- IceFireDB-Redis-proxy：Redis database proxy meets P2P, an interesting attempt.
-
IceFireDB-SQLite: Interesting When P2P Meets SQLite
you can browse: https://github.com/IceFireDB/IceFireDB/tree/main/IceFireDB-SQLite
https://github.com/IceFireDB/IceFireDB/tree/main/IceFireDB-SQLite
We are participating in a hackathon, using the P2P infrastructure of IPFS to connect to the SQLite storage engine. The team feels that it is quite interesting.
If you like it, please give a star, thank you.
- IceFireDB-SQLite: Interesting when P2P meets SQLite.
- Redcon - Redis compatible server framework for Rust
- IceFireDB adds OSS storage engine to help kv storage extend to OSS cloud storage, and supports Redis protocol.
- IceFireDB adds OSS storage engine to help KV storage extend to OSS cloud storage
- IceFireDB：A database that supports IPFS storage and Redis protocol, interesting direction.
act
-
Probing My SSD's Latency
The Aerospike ACT benchmarking tool characterizes flash devices on their latency under a fixed read/write profile. It won't tell you how fast your device is, it will tell you if a workload runs under a certain latency bound.
https://docs.aerospike.com/server/operations/plan/ssd/ssd_ce...
https://github.com/aerospike/act
If you set
max-lag-sec: 0 -
IceFireDB: Distributed disk storage database based on Raft and Redis protocol
It depends, yes but ... (not discounting any of the above).
One sees a lot of 3:1 in practice due to the replication factor. If you have 3 copies of the data and the client can read from any node, you get 3x the read performance as having to have a quorum write on two out of three nodes.
To the GP, for a rough swag of what is possible out of given hardware, a combination of FIO and ACT (measures IO latency under a fixed load) is a good start.
https://fio.readthedocs.io/en/latest/fio_doc.html
https://github.com/aerospike/act
What are some alternatives?
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
uhaha - High Availability Raft Framework for Go
fio - Flexible I/O Tester
ristretto - A high performance memory-bound Go cache
goleveldb - LevelDB key/value database in Go.
flashdb - FlashDB is an embeddable, in-memory key/value database in Go (with Redis like commands and super easy to read)
redix - a very simple pure key => value storage system that speaks Redis protocol with Postgres as storage engine and more
ledisdb - A high performance NoSQL Database Server powered by Go
space-daemon - The Space Daemon packages together IPFS, Textile Threads/Buckets, and Textile Powergate (Filecoin*) into one easy to install Daemon to make it easy to build peer to peer and privacy focused apps.
Tile38 - Real-time Geospatial and Geofencing
Olric - Distributed in-memory object store. It can be used as an embedded Go library and a language-independent service.