This is a function, not a bug. Different builders (and their respective employers) need various things. The Valkey group will construct an ideal product, and Redis will construct an ideal product. Both open supply. Everyone wins.
Would Trollope have most popular a smoother path thus far? Of course. “We…didn’t meet the open source community—and our community—where they are. I wish we had done better.” Fortunately, “that’s something that Salvatore has helped with a lot,” each giving us “a credible voice in the open source community” whereas additionally being “an incredible advocate for the company.” Oh, and he’s additionally an distinctive engineer: Sanfilippo is answerable for introducing Redis’ first new information kind in years (vector units). He’s a behind-the-scenes heavy affect on the pondering that led the corporate again to an open supply license, which has meant they’ll now fold in options from the Redis Stack modules (search, JSON, Bloom filters, and so on.) to unify their inside improvement processes whereas making a one-stop, real-time information platform.
“We think [changing to AGPLv3 is] the right thing to do for our users, and it’s the right strategic direction for the company,” says Trollope. It ought to guarantee a good higher Redis, whereas the Valkey fork, steered by an more and more numerous array of contributors from Alibaba, Google, Ericsson, Huawei, Tencent, AWS, and others, guarantees to present builders a robust various. Neither Redis nor Valkey are assured success. Both convey strengths and weaknesses. Developers (and their enterprise employers) will in the end determine, however no less than they now have a transparent selection between two nice options.