<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rowan Trollope on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/rowan-trollope/</link><description>Articles written by Rowan Trollope on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 May 2025 12:15:59 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/rowan-trollope/index.xml" rel="self" type="application/rss+xml"/><item><title>Redis is now available under the AGPLv3 open source license</title><link>https://foojayio.github.io/website/today/redis-is-now-available-under-the-agplv3-open-source-license/</link><pubDate>Fri, 02 May 2025 12:15:59 +0000</pubDate><guid>https://foojayio.github.io/website/today/redis-is-now-available-under-the-agplv3-open-source-license/</guid><description>&lt;p&gt;&lt;strong&gt;The rise of hyperscalers like AWS and GCP has unlocked incredible speed and scale for startups and enterprises alike. But for companies rooted in open source, it has posed a fundamental challenge: how do you keep innovating and investing in OSS projects when cloud providers reap the profits and control the infrastructure without proportional contributions back to the projects that they exploit?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;To counter this, companies like MongoDB and Elastic adopted SSPL to protect their business from cloud providers extracting value without reinvesting. Redis initially took a different approach, creating Redis Stack as a separate distribution with a different license for advanced features. While this safeguarded innovation, it also split the developer experience and slowed progress on core Redis. What we really needed was a way to enhance Redis at its core without maintaining two separate tracks&amp;mdash;Redis Community Edition and Redis Stack.&lt;/p&gt;</description></item></channel></rss>