Redis Core Team Update
Interesting move, putting “SLA-driven” infrastructure engineers (i.e. people working at public clouds to deliver Redis-as-a-Service solutions) in charge of the project. (Not just these two from AWS and Alibaba Cloud, but the rest being from Redis Labs.)<p>It seems like, for one reason or another (Redis Labs because they want to sell their “core plus proprietary modules” service; the clouds because they want to push you to use their other products for use-cases that fit them better), all the new leadership has reason to want to <i>not</i> add any more developer-facing features to Redis Core. I expect the Redis Core you see right now, is the same Redis Core we’ll have 10 years from now, client-API wise. Redis, as a USP, is “done.”<p>Unless, that is, some third-party comes in with their own polished feature PR, and pushes really hard for it. In other words, Redis is kind of moving to the Linux kernel model, where “new use-case out of nowhere” features come in mostly not from internal development, but rather from external contributors petitioning the core-maintainership priesthood with reasons their patch should be upstreamed.<p>Either way, there’ll certainly continue to be plenty of ops-staff-facing innovations, bug-fixes and polish. That’s what gets this new core team up in the morning. I’m sure people running Redis in production are happy about that.