Redis License Changes: Impact and Controversies

· algiegray's blog

Key takeaways:

  1. Redis has changed its license to a dual model, impacting managed service providers and open-source users.
  2. The new licenses, RSALv2 and SSPLv1, have restrictive terms that prevent commercial use without entering into commercial agreements.
  3. The change has sparked backlash from the open-source community and could lead to alternatives like KeyDB and Garnet.

Redis, a popular in-memory database vendor, has announced a shift to a dual-license approach, imposing more restrictive terms starting from Redis 7.4[4][5]. The new licenses, Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1), are not open-source and have caused controversy within the community.

# Restrictive Terms

The new licenses prevent commercial use without entering into commercial agreements with Redis. This change affects managed service providers and open-source users who rely on Redis for their solutions[4].

# Backlash from the Open-Source Community

The decision has sparked backlash from the open-source community, with discussions taking place on openSUSE and Fedora mailing lists. Alternatives like KeyDB, a still BSD-licensed fork, and Microsoft's Garnet are already available[4].

# Growing Desperation in FOSS Community

The Redis license change reflects the growing desperation in the free and open-source software (FOSS) community to make open source pay. Developers are resorting to sabotaging their own code, stopping free community support, and attempting sponsorship approaches[4].

# The SSPL and the AGPL

The SSPL is close to the GNU Affero General Public License (AGPL), with clause 13 requiring the provision of Service Source Code via network download at no charge. This extension of the AGPL, which closes the loophole in the GPL for SaaS apps, has upset open-source folks[4].

In conclusion, Redis' license change has significant implications for the open-source community, managed service providers, and users. The restrictive terms and backlash from the community highlight the challenges faced by the FOSS community in monetizing open-source projects.

Summary for: Youtube