redisraft
s3-benchmark
| redisraft | s3-benchmark | |
|---|---|---|
| 8 | 4 | |
| 801 | 776 | |
| 0.6% | - | |
| 7.4 | 0.0 | |
| 10 months ago | 3 months ago | |
| C | Go | |
| GNU General Public License v3.0 or later | 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.
redisraft
- RedisRaft
- Consistent Raft clusters from multiple Redis instances
-
Redis persistence strong or best effort?
Honestly you are better running Etcd for this kind of stuff, or using https://github.com/RedisLabs/redisraft Trying to tweak Redis for transactions is possible but goes against the grain.
- Can Redis be used as a primary database?
-
A distributed Posix file system built on top of Redis and S3
Redis can be persisted with RDB and AOF, can also be replicated to another machine. In the cloud, you don't need to worry about that, hosted Redis are ready to use.
The is an ongoing effort [1] to improve the persistency and availability in general, which is expected to be GA in 2021.
[1] https://github.com/RedisLabs/redisraft
s3-benchmark
- S3 Benchmark: Measure Amazon S3's performance from any location
- S3 Benchmark
-
Ask HN: Have you ever switched cloud?
There's another benchmark somewhere showing S3 can max out a 100Gbps instance.
https://github.com/dvassallo/s3-benchmark
Another potential issue is ListBucket rate limiting. If you have lots of small objects, you'll spend most of the time waiting to discover the names than transferring data
-
A distributed Posix file system built on top of Redis and S3
TTFB in S3 is 20-30ms around the 50th percentile. it can go much higher at p99 [1]. In any case, rotational latency for HDD drives is an order of magnitude lower (typically 2-5ms for a seek operation).
S3 is great for higher throughput workloads where TTFB is amortized across larger downloads (this is why it's very common to use S3 as a "data lake" where larger columnar files are stored, usually at the order of hundreds of MiB).
I think it's an interesting project but perhaps explaining the use cases where this solution is beneficial would go a long way here.
[1] https://github.com/dvassallo/s3-benchmark
What are some alternatives?
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
warp - S3 benchmarking tool
awesome-go-storage - A curated list of awesome Go storage projects and libraries
s5cmd - Parallel S3 and local filesystem execution tool.
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
bencher - benchmarks for operations with proto data in redis
rpCheckup - rpCheckup is an AWS resource policy security checkup tool that identifies public, external account access, intra-org account access, and private resources.
etcd - Distributed reliable key-value store for the most critical data of a distributed system