You Never Know When You Need a Fork
summary
A drop-in fork of the last open Redis commit becomes Valkey, joined the Linux Foundation in one week and ships its first release in two weeks, aiming full compatibility while reimplementing clients and packaging for major distros. Community-backed with over 40 corporate supporters, 87 unique code contributors and roughly 600 commits in six months, the project rebuilds lost infrastructure (clients, packaging) but struggles to reproduce prior performance benchmarks and discovers the website and some tooling were not actually open source.
AI-written summary · about
chapters (12)
- 0:00Redis fork story
- 1:28What is Valky
- 3:57Redis types and databases
- 6:31Redis history 2009-2024
- 10:24Open source promises
- 13:14License change and Valky
- 13:57Redis forks and alternatives
- 16:24Open governance for Valky
- 16:47Valky project state
- 19:57Valky success factors
- 22:04Fork challenges
- 24:14Valky community project
related talks
32mYou Never Know When You Need a Fork: Lessons Learned Building...
05mKeynote: Your Core Infrastructure Should Be Vendor Neutral and Open Source
34mTwo Hard Things: Naming Things & Cache Invalidation, Valkey Edition
33mValkey in Telecom: Leveraging Open Source for Unique Needs and G...
29mPlan to fork (So you don't have to fork)
44mFORK IT ALL if You Fork It
22mLessons from HasGeek's FOSS Journey
23mTowards a Better Adoption Model