This can be a function, not a bug. Completely different builders (and their respective employers) need various things. The Valkey neighborhood will construct an excellent product, and Redis will construct an excellent product. Each open supply. Everybody wins.
Would Trollope have most well-liked a smoother path thus far? After all. “We…didn’t meet the open supply neighborhood—and our neighborhood—the place they’re. I want we had performed higher.” Luckily, “that’s one thing that Salvatore has helped with lots,” each giving us “a reputable voice within the open supply neighborhood” whereas additionally being “an unimaginable advocate for the corporate.” Oh, and he’s additionally an distinctive engineer: Sanfilippo is liable 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 inner growth processes whereas making a one-stop, real-time information platform.
“We predict [changing to AGPLv3 is] the proper factor to do for our customers, and it’s the proper strategic path for the corporate,” says Trollope. It ought to guarantee an excellent 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 provide builders a robust different. Neither Redis nor Valkey are assured success. Each convey strengths and weaknesses. Builders (and their enterprise employers) will in the end determine, however a minimum of they now have a transparent alternative between two nice options.