You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could create a simple starter from scratch or fork and rebrand spring-boot-starter-data-redis (see here). Since we forked and rebranded spring-data-redis, I think that would be the best approach (and would ensure we capture all necessary Spring Boot functionality).
Note that the Spring Boot repo main branch is now 4.x RC, which is a huge change to the module structure and many breaking changes (Jakarta EE 11, JDK 21, Spring Framework 7.x, package/property renaming, etc). We will need to copy the source from the older v3.5.1 branch to align with our version of Spring Data Valkey. From there we should be able to rebrand the module for Valkey like what was done for Spring Data Valkey. We will also need to rearrange our Spring Data Valkey repo to accommodate multiple modules (Spring Data Valkey, Spring Boot Starter, and any other in the future).
Upgrading to Spring Boot 4.x (and Spring Data Valkey 4.x) in the future will be a very large effort due to all the breaking changes.
Copy just the Redis classes/files from spring-boot repo (from version 3.5.1 to align with spring-data-valkey)
Commit spring-boot-starter-data-valkey module to branch in spring-data-valkey
⭐ Update the Redis starter to work standalone (spring-boot is a monolith that includes all starters, verify by running unit tests)
Move to Maven instead of Gradle, and add basic README
⭐ Rebrand all packages, classes, properties, resources, etc to Valkey
⭐ Add support for Valkey GLIDE driver (requires complete Valkey GLIDE implementation in spring-data-valkey)
Create a Spring Boot example (for template and repositories using Spring Boot) under the examples module in spring-data-valkey
⭐ Test spring-data-examples repo and other examples using spring-boot-starter-data-valkey
Organize the repo to have multiple modules: spring-data-valkey, spring-data-valkey-examples, and spring-boot-starter-data-valkey (as a separate PR)
After getting the Redis starter to compile and run unit tests standalone, rebranding (and adding Valkey GLIDE support) and testing will take the bulk of the effort.
Is it currently possible to update dependencies from a remote repository using MavenCentral?
Hi @bluayer, we are working on publishing spring-data-valkey to Maven in the coming days, and will publish the Spring Boot starter in Maven in the next release. Until then the only options are to either build locally or download the artifacts from the 0.1.0 release.
Activity
jeremyprime commentedon Oct 20, 2025
We could create a simple starter from scratch or fork and rebrand
spring-boot-starter-data-redis(see here). Since we forked and rebrandedspring-data-redis, I think that would be the best approach (and would ensure we capture all necessary Spring Boot functionality).jeremyprime commentedon Oct 21, 2025
It is recommended to have both Spring Data Valkey and the Spring Boot starter as separate modules in the same repo.
For example see the following examples that have both modules in the same repo:
jeremyprime commentedon Nov 4, 2025
Note that the Spring Boot repo main branch is now 4.x RC, which is a huge change to the module structure and many breaking changes (Jakarta EE 11, JDK 21, Spring Framework 7.x, package/property renaming, etc). We will need to copy the source from the older v3.5.1 branch to align with our version of Spring Data Valkey. From there we should be able to rebrand the module for Valkey like what was done for Spring Data Valkey. We will also need to rearrange our Spring Data Valkey repo to accommodate multiple modules (Spring Data Valkey, Spring Boot Starter, and any other in the future).
Upgrading to Spring Boot 4.x (and Spring Data Valkey 4.x) in the future will be a very large effort due to all the breaking changes.
jeremyprime commentedon Nov 12, 2025
High-level plan:
spring-bootrepo (from version 3.5.1 to align withspring-data-valkey)spring-boot-starter-data-valkeymodule to branch inspring-data-valkeyspring-bootis a monolith that includes all starters, verify by running unit tests)spring-data-valkey)examplesmodule inspring-data-valkeyspring-data-examplesrepo and other examples usingspring-boot-starter-data-valkeyspring-data-valkey,spring-data-valkey-examples, andspring-boot-starter-data-valkey(as a separate PR)After getting the Redis starter to compile and run unit tests standalone, rebranding (and adding Valkey GLIDE support) and testing will take the bulk of the effort.
jeremyprime commentedon Dec 2, 2025
Follow-on tasks:
spring-data-valkey,spring-boot-starter-data-valkey,examples,performance)smoke-tests,spring-session-data-valkey, and others in the futurebluayer commentedon Dec 3, 2025
Is it currently possible to update dependencies from a remote repository using MavenCentral?
jeremyprime commentedon Dec 3, 2025
Hi @bluayer, we are working on publishing
spring-data-valkeyto Maven in the coming days, and will publish the Spring Boot starter in Maven in the next release. Until then the only options are to either build locally or download the artifacts from the 0.1.0 release.ikolomi commentedon Dec 29, 2025
@bluayer
Please note the alpha is available in maven: https://central.sonatype.com/artifact/io.valkey.springframework.data/spring-data-valkey/0.1.0