redisraft

So did mongodb. Then we all grew up, and went back to postgres. And your company took a stab at doing it right [1], though by that point most competent programmers decided that redis was just a smarter memcache and started designing around data loss instead of building on top of the programmable memory system you envisioned. [1] https://github.com/RedisLabs/redisraft

follow https://github.com/RedisLabs/redisraft/

The issue with Redis is that it's distributed story is not great. I wonder if their Raft experiment is finally GA or not. https://github.com/RedisLabs/redisraft

As mentioned in other place, the perfect solution would be adding Raft to redis [1]. [1] https://github.com/RedisLabs/redisraft

Redisraft [1] is a good thing to expect. [1] https://github.com/RedisLabs/redisraft

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

> It's clear this project did not start with exhaustive unit tests. I can't speak to "exhaustive", but Redis-Raft did have an extant unit and integration test suite prior to our collaboration. Here's what they looked like: https://github.com/RedisLabs/redisraft/tree/ff9fb28c74db880c... I'm hesitant to draw too strong a conclusion here, and I can't speak for the Redis Labs team, but I do suspect that this is somewhere where... having an outside tester, like Jepsen (or a suitably adversarial QA team) can help detect missing-stairs sorts of problems. Coming from the perspective of a prospective operator (and having some experience with testing distributed systems), I immediately said "of course I want proxy mode by default", when this wasn't how the Redis-Raft designers necessarily intended things to be used--they intended smart clients to m