<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.
aphyr: distributed systems are difficult and break in ways that are difficult to predict, this is known scientific fact and here's a long list of databases I broke because their engineers think the rules don't apply to them.
antirez: no, u!
elktown: both sides are tribals with superiority complexes!
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.
elktown · · focus · HN ↗
Yeah, as usual with devs; pick a tribe then go to insufferable lengths with the newfound and completely unearned superiority complex.
za_creature · · focus · HN ↗
antirez: no, u!
elktown: both sides are tribals with superiority complexes!
elktown · · focus · HN ↗
za_creature · · focus · HN ↗
Cause he did fuck up, then changed the subject, then claimed the criticism was unfair because he was clearly talking about something else.