🐾What comes after Redis?🐾
🤓 After recent announcement Redis is dumping open-source product, the community started discussions regarding fairness of that decision. But aside from this, developers should consider using other products as a replacement. So, what comes after Redis?
1️⃣ Valkey
As many of you are aware, AWS team was one of the main contributors while Redis was open-sourced product. And now AWS is committed to supporting open-source fork of Redis named Valkey. They are adding Valkey support to ElastiCache and MemoryDB managed database services. Moreover they backup Valkey together with Google Cloud, Oracle, Alibaba Cloud and other large companies. You can find more information on why AWS decided to support Valkey in official blogpost.
2️⃣ Garnet
For the ones who want to assess all the alternatives, because of forced migration -Microsoft launched Garnet. It is an open-source .NET alternative which advertised to be much faster than Redis. Microsoft claims it is compatible with existing Redis clients and it is provided under MIT license.
3️⃣ Other
There are other forks of Redis, such as Redict, which are supposed to be supported by AWS’s employee Madelyn Olson (Valkey fork creator). Also, there are several alternatives to Redis, which are fully compatible and easy to migrate: DragonflyDB, KeyDB and many others.
Which option is the best choice for your case depends on non-functional requirements of your workload. But definitely it will be an interesting thing to see how this alternatives will evolve and which features they will offer.
Thank you for reading, let’s chat 💬
💬 Do you use Redis in your workloads?
💬 Have you already choose the alternative you want to go with?
💬 Which challenges do you anticipate while migrating?
I love hearing from readers 🫶🏻 Please feel free to drop comments, questions, and opinions below👇🏻
