KeyDB as a [possible] replacement for Redis

PLEASE NOTE: our blog has MOVED to https://blog.flant.com/! New articles from Flant’s engineers will be posted there only. Check it out and subscribe to keep updated!

What if I tell you that there is a faster alternative to Redis? KeyDB is a relatively young and little-known project that lacks broad public coverage as of now. We have recently got the chance to use it, and now are eager to share our experience.

The backstory is rather trivial: one day, a massive influx of traffic led to significant degradation of a web application performance (namely, the response time). At that moment, we failed to diagnose the root of the problem, so we have decided to conduct several load tests later. During the testing, we found out the bottleneck in the system, which was the cache of the Redis database. As is often the case, for various reasons at that moment, we could not solve the problem the correct way (by asking developers to change the application logic). Being curious, we tried to find out an elegant and simple workaround. And that is how this article came into existence.

Please, read the rest here.