It is a characteristic, not a bug. Completely different builders (and their respective employers) need various things. The Valkey group will construct an excellent product, and Redis will construct an excellent product. Each open supply. Everybody wins.
Would Trollope have most popular a smoother path so far? After all. “We…didn’t meet the open supply group—and our group—the place they’re. I want we had performed higher.” Thankfully, “that’s one thing that Salvatore has helped with lots,” each giving us “a reputable voice within the open supply group” whereas additionally being “an unbelievable advocate for the corporate.” Oh, and he’s additionally an distinctive engineer: Sanfilippo is liable for introducing Redis’ first new knowledge sort 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 forth.) to unify their inner growth processes whereas making a one-stop, real-time knowledge platform.
“We expect [changing to AGPLv3 is] the precise factor to do for our customers, and it’s the precise strategic path for the corporate,” says Trollope. It ought to guarantee a fair higher Redis, whereas the Valkey fork, steered by an more and more various array of contributors from Alibaba, Google, Ericsson, Huawei, Tencent, AWS, and others, guarantees to present builders a powerful various. Neither Redis nor Valkey are assured success. Each convey strengths and weaknesses. Builders (and their enterprise employers) will in the end resolve, however not less than they now have a transparent selection between two nice options.
