4 ms·
To rephrase antirez from the previous thread: People use Redis, in large part, for its time and space guarantees on data structure operations. (Without those,
by derefr 13y ago
To rephrase antirez from the previous thread:
People use Redis, in large part, for its time and space guarantees on data structure operations. (Without those, you may as well be using a serialized object store.) Strong consistency requires rollbacks; and the book-keeping necessary to do rollbacks throws away the time and space guarantees. So either you have Strong Consistency, or you have Redis, but you don't get both.
But Redis Cluster is a compromise: something which is roughly good enough for most cases people actually use Redis for, while failing horribly at things Redis isn't used for anyway, and still providing Redis's time and space guarantees.
Theorists balk, because there are obvious places where Redis Cluster falls down, and they can demonstrate this. Engineers shrug, because Redis isn't being used in their companies in such a way that those demonstrations are relevant to their problems.
Most people who need Redis Cluster have already Greenspunned a Redis Cluster themselves, and they're already happily living with the compromise it entails. They'll gladly hand the support burden of writing cluster-management code upstream to antirez; it won't change any of the facts about the compromise.
- moe 13y agoMost companies also simply don't have redis-type data problems that can't be solved by throwing a pair of 768G ($40k) or 2TB servers ($120k) at them. When that option is available it tends to beat complex software solutions in every way.