The open-source community and giant cloud providers like Amazon Web Services (AWS), Google Cloud Platform (GCP), and Azure have always had a complex relationship. One of the most compelling stories that highlights this tension is the saga between Redis Labs and these tech giants.
The Genesis of Redis
Before diving into the complexities, it’s important to understand what Redis is. Redis, which stands for Remote Dictionary Server, is an open-source, in-memory database, cache, and message broker. Redis was released back in 2009 by Salvatore Sanfilippo.
Known for its high performance, Redis has become the go-to solution for many organizations that require a fast, reliable, and scalable data store. As of its popularity, it didn’t take long for cloud providers to integrate Redis into their service offerings.
The ‘Incomplete’ Redis on the Cloud
AWS, GCP, and Azure offer what seems like Redis as a service. However, there’s a catch. While it may look and feel like Redis, the version offered by these cloud providers lacks several essential features.
In 2018, Redis Labs updated its open-source licensing, effectively restricting the use of its proprietary add-on modules by third-party commercial vendors like AWS and Google. This was a strategic move designed to prevent these tech giants from offering the full Redis experience.
Jason Plotch makes a fun comparison on LinkedIn by making an analogy between Redis Enterprice, AWS Elasticache and Matrix:
Morpheus: The red pill, Redis Enterprise, offers you the truth of in-memory power. With unparalleled speed, your data will be accessed in the blink of an eye. Redis Enterprise allows you to manipulate reality, bending it to your will. It scales effortlessly, distributing data across clusters, and provides you the tools to craft your own destiny.
Neo: “And the blue pill?”
Morpheus: “The blue pill, Amazon ElastiCache, lets you remain in the realm of familiarity. It’s like the dream you choose to stay in, relying on conventional caching methods. But beware, Neo, for while it may seem comfortable, you’ll be bound by the limitations of the ordinary. Your data’s potential will be capped, much like your perception of reality.” — Jason Plotch
The Strategy Behind Redis’ Licensing Change
Redis Labs didn’t change their licensing structure on a whim. Cloud providers have a track record of repackaging successful open-source projects into proprietary services for profit.
Examples include AWS Elasticache, Azure Cache, and GCP Memorystore, among others. These cloud services generate significant revenue, often in the millions, if not billions. And yet, according to Redis Labs, these companies contribute little or nothing back to the original open-source communities that nurtured and developed these technologies.
The Philosophical Underpinnings
This battle is not just about technology; it’s also a philosophical debate about the nature of open-source software and the ethics of business practices in the tech world.
Open-source projects thrive on community contribution, shared knowledge, and the ideal that software should be accessible and customizable for the end-users. When giant cloud providers repurpose this communal work for profit without significant contribution, they arguably violate the spirit of open-source.
Redis Is Not Alone
One of the most high-profile cases is that of Elastic, the company behind Elasticsearch. Elastic changed its license from Apache 2.0 to a Server Side Public License (SSPL) to restrict cloud providers from offering Elasticsearch as a service without contributing back. This move ignited significant debate within the tech community.
MongoDB, a popular NoSQL database, also switched its license to the Server Side Public License (SSPL) in 2018. The intent was similar: to prevent cloud providers from repackaging MongoDB as a service without contributing back to the project. MongoDB’s shift was among the first that put the issue into the spotlight.
Conclusion
Redis Labs has taken a bold stand against the trend of cloud providers profiting from open-source projects without adequate contribution. By altering their licensing terms, they’ve made it more challenging for AWS, Azure, and Google Cloud Platform to offer complete Redis services. The battle lines are drawn, and the stakes are high, both economically and philosophically.
Understanding this issue in all its depth can empower users to make informed choices in a complex landscape, ensuring maximum benefit from the technologies they opt to use.
The story of Redis versus the cloud giants serves as a poignant reminder of the ongoing tension between open-source initiatives and commercial interests. It beckons us to consider what kind of technological world we want to live in — and what steps we can take to shape it.
For those committed to leveraging the full power of Redis, the choice is clear: Redis Enterprise offers a comprehensive range of features that are not available in scaled-down, cloud-provider versions. To dive deeper into the Redis licenses, you can check out Redis Licenses. And to learn more about these differences, you can check out the resources below:
Leave a Reply