The person who needs a Redis replacement but isn't interested in selling something that isn't core to their business and wants some assistance in the development from other people who are like minded.

They may or may not be a fool but their are more returns than just licensing fees for such a project prestige and it's effect on hiring for a company. Developer happiness. Other similar intangibles.

It seems to me, in the long run, it'd be cheaper to pay Redis for whatever they offer instead of attempting to craft your own solution, maintain it, and find others who also will maintain it. Developer happiness and exposure doesn't pay the rent.

Here’s two I found with a simple search of github.

https://github.com/yinqiwen/ardb https://github.com/yongman/tidis

No idea if they’re any good. Ardb looks interesting.

It's an in-memory key-value store. Its primary function is to let transient processes not have to hit the disk to update state. Go ahead and write one this weekend, in that shiny new language that you're interested in, and then finish it up by adjusting the redis bindings of a popular CMS to work with your daemon as well.

If it's so easy, I'm sure we'll see replacements of equal quality. The initial Redis release was in 2009. I would think it's unlikely you're going to reach the same feature and stability parity orders of magnitude faster that Redis did.

Certainly, it'll be a lot easier if you pick your redis-user in advance and look what its actual requirements are, so that you can focus on a solid implementation of those features.

You don't have to write a replacement, just fork Redis and continue from there.

A collaboration between the very cloud providers this seems to be a rant against?