The Downfall of Redis

Concise summary

Redis began as an in‑memory datastore to solve real‑time analytics and performance limits of disk‑backed systems. Over time it became a widely adopted building block (caching, queues, timelines) and was commercialized by a company that rebranded to Redis. In March 2024 the project’s license moved from permissive BSD to a dual source‑available model (SSPL + RSAL 2.0), explicitly restricting cloud/hosted use and removing Redis from OSI’s definition of “open source.” That change prompted community backlash, contributor departures, and renewed interest in open alternatives and forks.

Origin and technical motivation

• Redis started in 2007 when Salvatore “antirez” Sanfilippo created an in‑memory store (initially to fix MySQL‑based real‑time visitor‑tracking problems, project “LLOOGG”).
• Key technical insight: keeping data in memory (instead of disk) enabled low latency and high throughput required for real‑time analytics and timelines.
• Redis grew into a common infrastructure component used by companies such as Instagram, GitHub, and Twitter for caches, queues, timelines, and other low‑latency systems.
• The core was open‑sourced (published on GitHub in 2009), which accelerated adoption and community contribution.

Commercialization and company history

• Early sponsorship and commercialization:
  • VMware/Pivotal sponsored Antirez early on.
  • Consulting firms (e.g., Garantia Data) and a startup that became Redis Labs offered commercial services around Redis.
• Antirez transferred IP/trademarks to Redis Labs and joined the company; he later left the project in 2020, citing trust in the community and Redis employees to continue stewardship.
• Redis Labs rebranded to Redis (the company), took VC funding (hundreds of employees, ~$347M+ fundraised), and provided hosted Redis services competing with cloud offerings such as AWS ElastiCache.

License change (March 20, 2024): what changed, technical/legal implications

• What changed:
  • Redis moved from the permissive 3‑clause BSD (OSI‑approved) to a dual source‑available model:
    • SSPL (Server Side Public License) — originally created by MongoDB; it requires entities offering the software as a service to open‑source the entire service stack (management, UI, APIs, automation, monitoring, backups, storage, etc.). The OSI did not approve SSPL because of its usage restrictions.
    • RSAL 2.0 (Redis Source Available License 2.0) — does not force publication of service source, but it restricts making the software’s functionality available as a service to third parties; scope and enforceability are more vague than a permissive license.
• Legal and ecosystem implications:
  • Redis no longer meets OSI’s definition of “open source.”
  • Cloud providers (e.g., AWS, Alibaba) are explicitly restricted from offering hosted Redis without a commercial agreement with Redis the company.
  • The licensing is targeted at hosted/cloud usage and changes the balance between community development and commercial control.

Redis no longer counts as “open source” per OSI; the licensing explicitly targets hosted/cloud usage.

Consequences, community reaction, and alternatives

• Community reaction and fallout:
  • Significant negative reaction from contributors and users; some contributors publicly left or announced they would stop contributing (including an AWS contributor, Madeleine Olsen).
  • The license‑change pull request and announcement drew heavy pushback.
  • Concerns were raised about relicensing code originally contributed under BSD and removal of BSD notices, creating uncertainty about contributor rights.
• Likely motivations and leadership context:
  • Interpreted as pressure to monetize core infrastructure and extract revenue from cloud providers (VC/investor incentives).
  • The announcement came under CEO Rowan Trollope (after co‑founder Ofer Bengal stepped down), reinforcing perceptions of a profit‑driven strategy.
• Practical fallout and alternatives:
  • Many projects can migrate to open alternatives with relatively low friction.
  • Known alternatives and replacement paths:
    • KeyDB — open‑source, drop‑in Redis replacement.
    • Microsoft Garnet — an open cache store compatible with Redis clients.
    • Potential cloud provider forks (similar to the OpenSearch/Elasticsearch split), e.g., AWS could fork or provide a compatible service.
  • For new projects, choosing open alternatives reduces vendor/legal risk; for existing projects, migration paths are realistic for most use cases.

Technical takeaways

• Redis’s core technical value—fast in‑memory storage for low latency and high throughput—remains unchanged.
• The licensing change undermines ecosystem portability and raises vendor/legal risk for users who depend on hosted/managed Redis services.
• The incident highlights a recurring tension: stewardship of foundational open infrastructure vs VC/monetization strategies. Projects and teams should weigh license risk when choosing infrastructure components.

Recommended sources / further reading

• Salvatore “antirez” Sanfilippo — farewell blog post and personal blog (history, views, projects).
• Redis (the company) — official license change announcement and FAQs.
• Momento blog post — analytical writeup referenced in coverage and videos.
• SSPL (MongoDB) documentation and full texts of RSAL 2.0/SSPL for legal details.

Main speakers / sources referenced

• Salvatore “antirez” Sanfilippo (Redis founder)
• Redis (the company) and leadership: Ofer Bengal (co‑founder), Rowan Trollope (CEO at time of relicensing)
• Garantia Data / early commercial actors
• Madeleine Olsen (AWS contributor who publicly left)
• Alternative projects: KeyDB, Microsoft Garnet
• Commentary/analysis: Momento blog, Antirez’s blog, Redis company blog