Redis License Change Summary

 In Redis's official announcement, they said:

            "Beginning today, all future versions of Redis will be released with source-available              licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source             Available License (RSALv2) and Server Side Public License (SSPLv1).                                   Consequently,  Redis will no longer be distributed under the three-clause Berkeley               Software Distribution (BSD)."

Below is the license change summary:


    (This diagram is from Migrating from Redis to Valkey: The New Open-Source Alternative with AWS Support)

Comments

Post a Comment

Popular posts from this blog

IPv4/IPv6 Dual-Stack in Kubernetes

 Today, I was asked by a teammate to help troubleshoot an issue related to dual-stack in Kubernetes. It turned out that I am quite so unfamiliar with this subject. Actually, I didn't know some very basic things about it.  Hence I spent some time studying it. This post is a summary of it. What is IPv4/IPv6 dual-stack? IPv4/IPv6 dual-stack networking enables the allocation of both IPv4 and IPv6 addresses to Pods and Services. IPv4/IPv6 dual-stack networking is enabled by default for the Kubernetes cluster starting in 1.21, allowing the simultaneous assignment of both IPv4 and IPv6 addresses. IPv4/IPv6 dual-stack on Kubernetes cluster provides the following features:     Dual-Stack Pod networking(a single IPv4 and IPv6 address assignment per Pod)     IPv4 and IPv6 enabled Services     Pod off-cluster egress routing(eg. the Internet) via both IPv4 and IPv6 interfaces. IPv4/IPv6 Dual-Stack Prerequisites Kubernetes 1.20 or later Provider support for dua...
Read more

What happens under the hood when you create a Java ServerSocket and bind wildcard "0.0.0.0" in a dual-stack host?

Image
Today, I am busy helping a teammate to troubleshoot an issue in Kubernetes cluster. In the investigation, I found it is related to a question that I have been dying to figure out for a long time: what happens under the hood when you create a Java ServerSocket and bind wildcard "0.0.0.0", and this time, it is in a dual-stack host.   For example, in my WSL, it is a dual-stack: And then I run below Java program(just for testing): After I run it in my WSL, I use the netstat command to check the listening socket:  Although I am binding the "0.0.0.0" which is an IPv4 wildcard,  there's a tcp6 LISTENING socket with ":::8888" which is an IPv6 wildcard! So, why? What happens!? Let's delve into it. Firstly, let's check what happens when we create an InetSocketAddress with "0.0.0.0": It will try to resolve the hostname ("0.0.0.0" in our case): InetAddress.getByName(hostname). Let's find what does getAllByName do: private static I...
Read more