Valkey - Overview and Outlook - Dirk Hohndel, Verizon ![rw-book-cover](https://i.ytimg.com/vi/Qp74Nn-d5a8/maxresdefault.jpg) [[3. Resources/Readwise/Full Document Contents/Articles/Valkey - Overview and Outlook - Dirk Hohndel, Verizon|Full Document Contents]] ## Document Notes --- tags: - #opensource - #redis - #cloudinfrastructure Author: Dirk Hohndel Source: [Valkey - Overview and Outlook - Dirk Hohndel, Verizon](https://www.youtube.com/watch?v=Qp74Nn-d5a8) Reference: [Page Link](https://www.youtube.com/watch?v=Qp74Nn-d5a8) date created: 2024-09-16 15:30 --- # Title: Valkey: Overview and Outlook ## Table of Contents:  - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes:]] - [[#🗣️ Paraphrase:]] - [[#📰 Newsletter:]] - [[#✅ Action Items:]] - [[#🧪 Hypotheses:]] - [[#📊 Methodology:]] - [[#❓ Questions:]] - [[#🔮 Future Research:]] - [[#💡 Implications:]] - [[#🧠 Learning Styles Assessment:]] - [[#📊 Accessibility Assessment:]] - [[#🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment:]] - [[#✅ Logical Validity:]] - [[#🔍 SEO Evaluation]] - [[#🎯 Conclusion]] ### References: - Dirk Hohndel, Verizon, [Valkey: Overview and Outlook](https://www.youtube.com/watch?v=Qp74Nn-d5a8) ## 📝 Summary: Dirk Hohndel discusses Valkey, an open-source project born from a fork of Redis after the company’s controversial licensing changes. The project is supported by major cloud players like AWS and aims to build a community-driven alternative with better performance and new features, ensuring it remains free and open-source. ## 📖 Main Content: Valkey is designed to be a fork of Redis, allowing open-source advocates to maintain control over the codebase. With contributors from major companies, it offers significant performance improvements and features like multi-threaded I/O operations, enhanced clustering, and support for JSON objects. Migration from Redis to Valkey is seamless, and the project has strong backing from the Linux Foundation. ### 🗒️ Notes: - **Valkey Origins**: - Forked from Redis after its license changed, making Redis no longer open-source. - Backed by large cloud providers like AWS. - **Key Features**: - Multi-threaded architecture improves I/O performance. - Enhanced clustering for scaling across multiple nodes. - Native support for JSON and full-text search capabilities. - **Migration from Redis**: - Migration tools allow seamless transition from Redis to Valkey. - Supports the same API and protocols as Redis, ensuring compatibility. - **Community Focus**: - Focused on fostering open-source contribution and community engagement. - The Linux Foundation oversees governance, ensuring long-term sustainability. ## 📖 References: - Dirk Hohndel’s presentation at Verizon: [Valkey: Overview and Outlook](https://www.youtube.com/watch?v=Qp74Nn-d5a8) ## 🗣️ Paraphrase:  1. Valkey, a fork of Redis, was created in response to Redis's licensing change, which closed off certain open-source freedoms. The goal of Valkey is to preserve the open-source nature of Redis while offering a superior community-driven alternative. 2. The Linux Foundation is a steward of Valkey, supporting its community-focused model. The project's rapid growth, with contributions from companies like AWS, shows promise for its future in cloud infrastructure. ## 📰 Newsletter: In this edition, we’re spotlighting **Valkey**, a fork of Redis that keeps your data open-source. Developed in response to Redis's licensing changes, Valkey is designed for cloud-scale performance with advanced features like multi-threaded I/O, JSON support, and seamless clustering. It’s backed by major players like AWS and the Linux Foundation, ensuring that it’s here to stay. Want to switch from Redis to Valkey? Learn more [here](https://www.youtube.com/watch?v=Qp74Nn-d5a8) and discover how to make the migration easy. ## ✅ Action Items: As a Developer Advocate, I can align this article with my focus on open-source advocacy by: - Encouraging the WordPress community to explore Valkey for their caching and database needs. - Demonstrating how Valkey enhances performance, keeping projects scalable and secure within an open-source framework. - Using this as an example of open-source resilience against closed licensing, aligning with my long-term goal of supporting sustainable open-source contributions. ## 🧪 Hypotheses: - Projects using Valkey will see a 20-30% reduction in memory footprint over Redis. - Adoption of Valkey by cloud providers will boost its popularity as the open-source default in database caching solutions. ### 📊 Methodology: - **Data Collection**: Gather performance data from companies migrating from Redis to Valkey. - **Research Design**: Compare memory and I/O performance between Redis and Valkey implementations. - **Analysis**: Analyze improvements in cloud scalability and developer adoption post-migration. ### ❓ Questions: - Will Valkey maintain its community-driven governance structure in the face of large corporate backing? - How does Valkey’s multi-threaded I/O compare to Redis in high-demand applications? ### 🔮 Future Research: - Explore the impact of Valkey's native JSON support on web application performance. - Investigate the role of open-source projects like Valkey in countering corporate control over foundational software. ### 💡 Implications:  Valkey could shift the open-source database landscape, giving developers more control and flexibility. Its success would encourage more companies to embrace open-source forks as a solution to restrictive licensing. ### 🧠 Learning Styles Assessment: #### Visual Learners (Spatial): - **Present**: Slides included but lacked visualizations of performance improvements. - **Improve**: Add infographics comparing Redis vs. Valkey performance metrics. #### Aural Learners (Auditory-Musical): - **Present**: The talk is rich in explanation, perfect for auditory learners. - **Improve**: Provide an accompanying podcast or audio summary. #### Verbal Learners (Linguistic): - **Present**: Strong verbal explanations, but could benefit from further storytelling or analogies. #### Physical Learners (Kinesthetic): - **Present**: Demonstration of Valkey's migration process in the talk. - **Improve**: Offer hands-on migration exercises or an interactive walkthrough. #### Logical Learners (Mathematical): - **Present**: Detailed logical reasoning about Valkey’s architectural improvements. - **Improve**: Include more structured data or graphs showing performance benefits. #### Social Learners (Interpersonal): - **Present**: Opportunities for community engagement are mentioned. - **Improve**: Highlight more case studies from the community to foster social learning. #### Solitary Learners (Intrapersonal): - **Present**: Opportunities for reflection on personal use cases and implementation strategies. - **Improve**: Provide questions to help individuals assess how Valkey could improve their projects. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure the talk transcript is accessible with proper headings and structure. - **Keyboard Navigation**: Encourage improvements to make the site keyboard navigable. - **Contrast and Readability**: Ensure high contrast for all presentation slides and video captions. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: Limited global examples. - **Inclusive Language**: Language was neutral and accessible, but more diverse case studies could be included. - **Representation**: Highlight more contributors from underrepresented groups in the Valkey project. - **Psychological Safety**: The project fosters open-source collaboration, though more focus on inclusivity could enhance engagement. ### ✅ Logical Validity:  The argument for Valkey’s benefits over Redis is well-structured, focusing on tangible improvements like performance, community governance, and openness. However, a clearer explanation of long-term governance structures could strengthen the argument further. - **Sound Deductive Reasoning**: The argument that Valkey's improvements make it a better option than Redis logically follows. - **Appeal to Fact > [!note]+ Document Notes > tags: > - #opensource > - #redis > - #cloudinfrastructure > Author: Dirk Hohndel > Source: [Valkey - Overview and Outlook - Dirk Hohndel, Verizon](https://www.youtube.com/watch?v=Qp74Nn-d5a8) > Reference: [Page Link](https://www.youtube.com/watch?v=Qp74Nn-d5a8) > date created: 2024-09-16 15:30 > > # Title: Valkey: Overview and Outlook > <!-- deep-read:sections start --> ## Table of Contents: 1. [📝 Summary](#-summary) 2. [📖 Main Content](#-main-content) 3. [🗒️ Notes](#-notes) 4. [🗣️ Paraphrase](#-paraphrase) 5. [📰 Newsletter](#-newsletter) 6. [✅ Action Items](#-action-items) 7. [🧪 Hypotheses](#-hypotheses) 8. [📊 Methodology](#-methodology) 9. [❓ Questions](#-questions) 10. [🔮 Future Research](#-future-research) 11. [💡 Implications](#-implications) 12. [🧠 Learning Styles Assessment](#-learning-styles-assessment) 13. [📊 Accessibility Assessment](#-accessibility-assessment) 14. [🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) 15. [✅ Logical Validity](#-logical-validity) 16. [🔍 SEO Evaluation](#-seo-evaluation) 17. [🎯 Conclusion](#-conclusion) ### References: - Dirk Hohndel, Verizon, [Valkey: Overview and Outlook](https://www.youtube.com/watch?v=Qp74Nn-d5a8) ## 📝 Summary: Dirk Hohndel discusses Valkey, an open-source project born from a fork of Redis after the company’s controversial licensing changes. The project is supported by major cloud players like AWS and aims to build a community-driven alternative with better performance and new features, ensuring it remains free and open-source. ## 📖 Main Content: Valkey is designed to be a fork of Redis, allowing open-source advocates to maintain control over the codebase. With contributors from major companies, it offers significant performance improvements and features like multi-threaded I/O operations, enhanced clustering, and support for JSON objects. Migration from Redis to Valkey is seamless, and the project has strong backing from the Linux Foundation. ### 🗒️ Notes: - **Valkey Origins**: - Forked from Redis after its license changed, making Redis no longer open-source. - Backed by large cloud providers like AWS. - **Key Features**: - Multi-threaded architecture improves I/O performance. - Enhanced clustering for scaling across multiple nodes. - Native support for JSON and full-text search capabilities. - **Migration from Redis**: - Migration tools allow seamless transition from Redis to Valkey. - Supports the same API and protocols as Redis, ensuring compatibility. - **Community Focus**: - Focused on fostering open-source contribution and community engagement. - The Linux Foundation oversees governance, ensuring long-term sustainability. ## 📖 References: - Dirk Hohndel’s presentation at Verizon: [Valkey: Overview and Outlook](https://www.youtube.com/watch?v=Qp74Nn-d5a8) ## 🗣️ Paraphrase: 1. Valkey, a fork of Redis, was created in response to Redis's licensing change, which closed off certain open-source freedoms. The goal of Valkey is to preserve the open-source nature of Redis while offering a superior community-driven alternative. 2. The Linux Foundation is a steward of Valkey, supporting its community-focused model. The project's rapid growth, with contributions from companies like AWS, shows promise for its future in cloud infrastructure. ## 📰 Newsletter: In this edition, we’re spotlighting **Valkey**, a fork of Redis that keeps your data open-source. Developed in response to Redis's licensing changes, Valkey is designed for cloud-scale performance with advanced features like multi-threaded I/O, JSON support, and seamless clustering. It’s backed by major players like AWS and the Linux Foundation, ensuring that it’s here to stay. Want to switch from Redis to Valkey? Learn more [here](https://www.youtube.com/watch?v=Qp74Nn-d5a8) and discover how to make the migration easy. ## ✅ Action Items: As a Developer Advocate, I can align this article with my focus on open-source advocacy by: - Encouraging the WordPress community to explore Valkey for their caching and database needs. - Demonstrating how Valkey enhances performance, keeping projects scalable and secure within an open-source framework. - Using this as an example of open-source resilience against closed licensing, aligning with my long-term goal of supporting sustainable open-source contributions. ## 🧪 Hypotheses: - Projects using Valkey will see a 20-30% reduction in memory footprint over Redis. - Adoption of Valkey by cloud providers will boost its popularity as the open-source default in database caching solutions. ### 📊 Methodology: - **Data Collection**: Gather performance data from companies migrating from Redis to Valkey. - **Research Design**: Compare memory and I/O performance between Redis and Valkey implementations. - **Analysis**: Analyze improvements in cloud scalability and developer adoption post-migration. ### ❓ Questions: - Will Valkey maintain its community-driven governance structure in the face of large corporate backing? - How does Valkey’s multi-threaded I/O compare to Redis in high-demand applications? ### 🔮 Future Research: - Explore the impact of Valkey's native JSON support on web application performance. - Investigate the role of open-source projects like Valkey in countering corporate control over foundational software. ### 💡 Implications: Valkey could shift the open-source database landscape, giving developers more control and flexibility. Its success would encourage more companies to embrace open-source forks as a solution to restrictive licensing. ### 🧠 Learning Styles Assessment: #### Visual Learners (Spatial): - **Present**: Slides included but lacked visualizations of performance improvements. - **Improve**: Add infographics comparing Redis vs. Valkey performance metrics. #### Aural Learners (Auditory-Musical): - **Present**: The talk is rich in explanation, perfect for auditory learners. - **Improve**: Provide an accompanying podcast or audio summary. #### Verbal Learners (Linguistic): - **Present**: Strong verbal explanations, but could benefit from further storytelling or analogies. #### Physical Learners (Kinesthetic): - **Present**: Demonstration of Valkey's migration process in the talk. - **Improve**: Offer hands-on migration exercises or an interactive walkthrough. #### Logical Learners (Mathematical): - **Present**: Detailed logical reasoning about Valkey’s architectural improvements. - **Improve**: Include more structured data or graphs showing performance benefits. #### Social Learners (Interpersonal): - **Present**: Opportunities for community engagement are mentioned. - **Improve**: Highlight more case studies from the community to foster social learning. #### Solitary Learners (Intrapersonal): - **Present**: Opportunities for reflection on personal use cases and implementation strategies. - **Improve**: Provide questions to help individuals assess how Valkey could improve their projects. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure the talk transcript is accessible with proper headings and structure. - **Keyboard Navigation**: Encourage improvements to make the site keyboard navigable. - **Contrast and Readability**: Ensure high contrast for all presentation slides and video captions. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: Limited global examples. - **Inclusive Language**: Language was neutral and accessible, but more diverse case studies could be included. - **Representation**: Highlight more contributors from underrepresented groups in the Valkey project. - **Psychological Safety**: The project fosters open-source collaboration, though more focus on inclusivity could enhance engagement. ### ✅ Logical Validity: The argument for Valkey’s benefits over Redis is well-structured, focusing on tangible improvements like performance, community governance, and openness. However, a clearer explanation of long-term governance structures could strengthen the argument further. - **Sound Deductive Reasoning**: The argument that Valkey's improvements make it a better option than Redis logically follows. - **Appeal to Facts**: Performance improvements and examples from AWS and other companies provide solid evidence. ### 🔍 SEO Evaluation: 1. **Keywords**: - **Present**: Keywords like “Valkey,” “Redis fork,” and “open-source database” are present. - **Keyword Placement**: Well-placed throughout the content. 2. **Meta Description**: - **Present**: A meta description with the main keywords is present but could be more detailed. 3. **Title Tag**: - **Present**: Title includes main keywords and is concise. 4. **Headers**: - **Present**: Headers (H1, H2, H3) are appropriately used for readability. 5. **Content Length**: - **Present**: Sufficient length to cover the topic deeply. 6. **Internal and External Links**: - **Present**: Contains external links to the Valkey project and supporting sources. 7. **Image Optimization**: - **Alt Text**: Images should include alt text for accessibility. 8. **Mobile Optimization**: - **Responsive Design**: The video format and article content are mobile-friendly. 9. **User Engagement**: - **Time on Page**: Engaging content keeps users invested. - **Calls to Action**: Clear prompts to explore Valkey further. 10. **Schema Markup**: - **Rich Snippets**: Consider adding FAQ schema markup to boost SEO. 11. **Social Sharing**: - **Social Sharing Buttons**: Ensure sharing buttons are present on the page. ## 🎯 Conclusion: Valkey presents a compelling open-source alternative to Redis, combining better performance with community governance. With strong support from AWS and the Linux Foundation, it offers a promising future for developers seeking a scalable, community-driven key-value store. Short Summary for [Valkey - Overview and Outlook - Dirk Hohndel, Verizon](https://www.youtube.com/watch?v=Qp74Nn-d5a8) by [Merlin](https://merlin.foyer.work/) Title: Valky - Fork of Redis by Linux Foundation - License Controversy and Project Overview [00:04](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=4) Valky project overview and background [02:35](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=155) Valky 72 is a direct Fork of Redis with significant implications [05:16](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=316) Concerns about relicensing and the positive outlook for Valky project [07:50](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=470) Valky project gaining strong corporate support and contributor engagement. [10:23](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=623) Valky community addressing performance and observability challenges in Reddis [12:58](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=778) Enhancements in upcoming Valky release [15:38](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=938) Improved performance and scalability in Valky 8.0 [18:06](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1086) Consider migrating from Redis due to licensing issues [20:13](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1213) Optimizing memory usage and performance in large data sets [22:40](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1360) Smooth migration from Redis to Valkey with no-brainer compatibility [25:07](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1507) Easy data migration with Valky for large clusters [27:26](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1646) Encouraging diverse stories within the global community --------------------------------- Detailed Summary for [Valkey - Overview and Outlook - Dirk Hohndel, Verizon](https://www.youtube.com/watch?v=Qp74Nn-d5a8) by [Merlin](https://merlin.foyer.work/) Title: Valky - Fork of Redis by Linux Foundation - License Controversy and Project Overview [00:04](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=4) Valky project overview and background - Dirk Hohndel, from Verizon, discusses the move of Redis to non-open source licenses and the formation of the Valky project - Valky project formed by maintainers as a response to Redis license change, started before official announcement [02:35](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=155) Valky 72 is a direct Fork of Redis with significant implications - Forks are a fundamental right in open source projects, allowing for improvement and continuation under the same license - Red's move to relicensing indicates a lack of understanding of sustainable business models in open source [05:16](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=316) Concerns about relicensing and the positive outlook for Valky project - Community response to the relicensing as bait-and-switch - Positive indicators for the future success of Valky project [07:50](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=470) Valky project gaining strong corporate support and contributor engagement. - More than 40 companies see Valky as the future platform, including Dirk Hohndel's company. - Over 80 active contributors joined within the project's first five months, a strong sign for project health. [10:23](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=623) Valky community addressing performance and observability challenges in Reddis - Companies often face conflicts between open-source initiatives and commercial projects, hindering progress. - Valky community making significant changes in performance, memory footprint, infrastructure, and observability in Reddis, with upcoming features like native JSON data type. [12:58](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=778) Enhancements in upcoming Valky release - Introduction of native Bloom filter data type - Inclusion of full text search capability for web applications [15:38](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=938) Improved performance and scalability in Valky 8.0 - Enhanced ability to scale by taking advantage of multiple threads for IO operations - Significant performance improvement observed, especially in handling large data loads [18:06](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1086) Consider migrating from Redis due to licensing issues - Legal teams may recommend migration from Redis due to licensing conflicts - Migrate for better technology and community-driven development [20:13](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1213) Optimizing memory usage and performance in large data sets - Storing small data types like integers and small strings has a significant impact on memory footprint and performance - Removing one level of indirection in data structure design has a direct impact on memory footprint and performance [22:40](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1360) Smooth migration from Redis to Valkey with no-brainer compatibility - Both Redis 7.2 and Valkey 7.2 share identical code, configuration, API, commands, wire protocol for seamless transition - Client libraries remain the same, making the process straightforward for administrators [25:07](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1507) Easy data migration with Valky for large clusters - Utilize Valky for a seamless rolling update migration in cluster nodes - Multiple companies offering support and services for Valky, including Pona and others [27:26](https://www.youtube.com/watch?v=Qp74Nn-d5a8&t=1646) Encouraging diverse stories within the global community - Main interest in success and failure stories - Addressing issues, seeking feedback to improve community engagement <!-- deep-read:sections end --> ## Highlights - did this after repeatedly in the past saying that redis would forever be under the BSD license um and a lot of people who believe in open source a lot of people who used reddis under the terms of the open source licenses um were very unhappy with that understandably and so the timing that reddis did this was super interesting because they did it during Cube Con Europe so C con like this one there aren't a lot of them like three a year right and that's when everyone is together in the same place so all the companies who were most annoyed by R is doing this were already together in the same place and eight days later comes the announcement that valky is formed the maintainer themselves meline and a few others were actually ahead of this so they had already forked the code they had already started to create a new version but the Linux Foundation just over a week after the Redd announcement announced the creation of valky and a couple weeks later the first release of valky came out valky 72 which essentially is a direct Fork of redis and I I'll get to this later why this is important now there is there is a a very common misunderstanding of of two key facts that play into this and I want to really focus on those two key facts one Forks are good Forks are one of the key things that open-source licenses allow you so if whoever it is if the maintainer starts doing things you don't like you have the ability to Fork the code under the same license and do better so if you think lenus tals is not a good maintainer for the Linux kernel you can Fork it not sure how well this will go but more power to you and and this is something where people say oh you know the Linux Foundation is stealing the code no that's not what it is we are using one of the most basic fundamental rights in open- Source projects to be able to continue the project under the previous license so that's one and the other often voiced misconception is well but red is is right to do this because they need to be able to make money well open source is not a business model ([View Highlight](https://read.readwise.io/read/01j8005shez4jvrxra65wme5s5))