Hacker News Reader

Comment by greenavocado | Hacker News Reader

My theory is Redis is trying to take control over all popular libraries that interface with it so it can break protocol level compatibility to force vendor lock-in

View on HN

That would push everyone to valkey. They want to add proprietary features supported only by their server and client. That's the extend part of "embrace, extend, extinguish".

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

All of this drama is already doing that.

Some cash cows would remain stuck and they are ultimately the ones that would be milked for profit even if 95% of the community leaves

My theory as well. I would almost bet on it.

Redis is risking its reputation in order to solidify its revenue stream in the face is rising threats like Valkey, etc.

Well it's either solidify revenue stream or likely go out of business. And what's a reputation if there's no business to attach it to?

Are there many redis drop-ins alternatives?

Valkey is the fork/drop-in replacement from the Linux Foundation.

Valkey, dragonfly, kvrocks are all protocol-compatible and mostly drop-in replacements for upstream Redis.

If you want something hosted/managed, there’s Upstash Redis (though I reckon they’ll soon have to change the name of that offering).

Microsoft has also been working on one. https://microsoft.github.io/garnet/

Kvrocks is pretty substantially different, from my understanding. It only shares the protocol.

https://github.com/dragonflydb/dragonfly Is a multi-threaded drop in replacment

Tangential, I realized I can be satisfied by Redis from 2013. Who are relying on recent Redis versions?

Reply on news.ycombinator.com