<a href="https://aphyr.com/posts/307-jepsen-redis-redux" rel="nofollow">https://aphyr.com/posts/307-jepsen-redis-redux (see his comments there too)
He had an awesome opportunity to do high concurrency synchronous replication (raft) on top of in-memory databases at a time where ssds were still uncommon, but instead chose to redneck-engineer his own protocol, then double-down that he knows best.
Not that dissimilar to choosing C over rust for familiarity.
Redis remained useful for 10+ years because of the design choices that were made, actually. Many other systems/companies failed since the idea, back then, was that a system needed to be linearizable or could not be useful at all. So what you point as a limit of my work was one of the better things I did in my career.
Thanks, I believe the hate is also linked to my AI-positiveness... Funny enough GPT 6 Astra can easily produce a TLA+ model that can be verified under very real-world system model assumptions on the safety of RedLock, which is a paradox to the arguments I see in this thread and to the AI-rage.
jeffbee · · focus · HN ↗
wg0 · · focus · HN ↗
za_creature · · focus · HN ↗
<a href="https://aphyr.com/posts/283-jepsen-redis" rel="nofollow">https://aphyr.com/posts/283-jepsen-redis
<a href="https://antirez.com/news/55" rel="nofollow">https://antirez.com/news/55
finally
<a href="https://aphyr.com/posts/307-jepsen-redis-redux" rel="nofollow">https://aphyr.com/posts/307-jepsen-redis-redux (see his comments there too)
He had an awesome opportunity to do high concurrency synchronous replication (raft) on top of in-memory databases at a time where ssds were still uncommon, but instead chose to redneck-engineer his own protocol, then double-down that he knows best.
Not that dissimilar to choosing C over rust for familiarity.
antirez · · focus · HN ↗
jacquesm · · focus · HN ↗
I think OP wished he had that kind of credit to his name.
antirez · · focus · HN ↗