In the dynamic world of web hosting and online services, staying informed about licensing changes of widely used software components is crucial. Redis team recently announced a significant shift in their licensing model that could impact many developers and hosting providers.
What’s Changing with Redis?
Redis, the high-performance, open-source cache server, is transitioning its license from BSD to Server Side Public License (SSPL) starting with version 7.4. This move is designed to prevent third-party vendors from offering services, competing with Redis without open-sourcing their entire stack under the same license. This change reflects a growing trend among open-source projects to protect their ecosystem and ensure fair use by commercial entities.
When is the Change Happening?
The license switch is slated to occur with the release of Redis version 7.4. As of January 9, 2024, the current stable version is 7.2, giving developers and organizations time to prepare for this transition.
Why the Change?
The primary rationale behind adopting SSPL is to better distinguish the use of feature-rich Redis software by the community and their commercial users. Redis vendor wants to prevent cases when some providers will compete with Redis by building and offering some services based on Redis itself.
What Does It Mean for You?
For the vast majority of users, including software vendors and hosting customers, this license change will not affect their operations. If you’re leveraging Redis for caching within your web applications or internally within your organization, the new licensing terms do not apply. The shift primarily targets services directly competing with Redis or those heavily deriving their value from it.
Plesk Users: Why You’re in the Clear
For Plesk users, the transition to Redis’s new licensing model is seamless and worry-free, thanks to the platform’s Docker integration capabilities. This feature allows Plesk users to run Redis in a Docker container, ensuring that they can continue utilizing Redis without directly embedding it into their products or services. This utilization method aligns perfectly with the terms of the new Redis license as soon as Docker integration for Plesk was initially designed to utilize the same server resources. It’s also important that in case of usage with Plesk, Redis is utilized as a part of a web hosting offer, i.e., NOT as a Redis competitive solution.
(Read Plesk documentation of how to run additional services in Docker with Plesk for Free)
Looking Ahead
While changes in software licensing can sometimes introduce complexity and uncertainty, Plesk’s robust infrastructure and Docker integration feature provides a straightforward path forward for utilizing Redis. By leveraging Docker, Plesk users can continue to enjoy the performance benefits of Redis without concerns over licensing compliance.
For those impacted by the license change or seeking alternatives, options include using an open-source fork like Redict, exploring other caching solutions such as Memcached, or considering commercial licenses or Redis-as-a-service offerings that handle licensing terms on behalf of their users.
Redis license change marks a significant shift in how the software can be used commercially, however Plesk users should not worry. The platform’s Docker integration feature shields them from the complexities of this transition, affirming Plesk’s commitment to providing flexible, reliable web hosting solutions in an ever-evolving technological landscape.