> Redis is arguably the most well regarded tech of all.
REDIS tradeoffs have been so widely discussed because many, many engineers disagree with them. REDIS is so lowly regarded that some companies ban it completely, making their engineers choose between memcached or something more enterprisey (hazelcast these days, Coherence some time ago).
This comment has a lot of words but says nothing. "Many engineers" disagree with every piece of software, and "some companies" ban every piece of software.
Why are you writing Redis in all caps like it's an acronym? Reminds me of those old dog C programmers who write long rants about RUST with inaccuracies that belie the fact they've never actually used it.
If anything it's ReDiS, Remote Dictionary Server. Also pronounced to sound like 'remote', unlike the color of its logo (which would be spelled Reddis).
Why is Redis regarded so lowly?
Now, Redis Search, I understand. Very buggy, search index misses records and doesn't tell that it missed them and so on.
Probably the same reasons dynamically-scaled Aerospike is not as popular. Redis primarily has a reputation of just "caching" stuff in memory, but probably the rates of CVE in the distributed clients soured some peoples opinions.
Distributed systems is hard, and what seems like a trivial choice about design constraints can quickly balloon in cost. =3
I work at a company that banned redis after an outage. kind of blunt, it feels like such an amateur decision to have made. So reactionary instead of trying to learn it. It's large popular internet company too
I have a dedicated server that's running an instance of redis on each of the 32 cores and it's been up for over a year now. Each core is doing about 30k QPS
REDIS tradeoffs have been so widely discussed because many, many engineers disagree with them. REDIS is so lowly regarded that some companies ban it completely, making their engineers choose between memcached or something more enterprisey (hazelcast these days, Coherence some time ago).