As we’ve just shipped the fourth milestone release of Spring Data release train Kay, let’s take a look at the changes and features that come with the 13 modules on the train since our first milestone. This blog post covers a set of changes but is no means comprehensive of the 550+ changes between M2 and M4. To get a full list of changes, take a look into our Jira for Kay M1, M2, M3, and M4 changes.

Here’s a curated list of our key changes:

• Adjustments in the reactive support

• Composable repositories

• Improved naming scheme for CRUD methods

• Fluent MongoOperations API

• Kotlin extension for MongoDB’s Template API

• MongoDB Collation Support

• Redis client configuration

• Cassandra Lightweight transaction support and Query/Update objects

• Java 9 compatibility

• Upgrade to Elasticsearch 5.4

…

On behalf of the Spring Data team, I'd like to announce the availability of the fourth Spring Data Kay milestone. This release ships 98 tickets fixed along with some notable changes like composable repositories, the fluent MongoDB collection operation API, Kotlin extension for MongoDB, and much more.

This milestone is going to be picked up by Spring Boot 2.0 M2 and we're heading towards a release candidate within the next month. We'll publish a follow-up blog post with an in-depth discussion of the new features added to the milestone in the upcoming days.

Find the complete list of issues fixed here…

On behalf of the Spring Data team, I'd like to announce the availability of Ingalls SR4 and Hopper SR11 service releases. Both of them ship 60 issues fixed in total. Service releases are bugfix ones and recommended upgrades for all users. The releases are going to be picked up by the upcoming Boot 1.5 and 1.4 services releases for your convenience.

The complete list of issues fixed for Ingalls SR4 can be found here, the one for Hopper SR 11 here.

Spring Data Ingalls SR4

• Spring Data Commons 1.13.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data JPA 1.11.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data KeyValue 1.2.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data for Apache Cassandra 1.5.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data for Apache Solr 2.1.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Gemfire 1.9.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Neo4j 4.2.4 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data MongoDB 1.10.4 - Artifacts - JavaDocs - Documentation - …

On behalf of the Spring Data team, I’d like to announce the availability of the third milestone of the release train Kay.

The most significant change is an improved naming scheme for CrudRepository. We extracted the store-specific CustomConversions to Spring Data Commons and introduced bi-directional type-based converters to maintain a single API for common conversion code. You can now define converters using lambdas. You need to adopt your code to the renamed methods. MongoDB ships with a renamed annotation for reactive tailable cursors, we renamed @InfiniteStream to @Tailable. Users of…

On behalf of the community, it's my pleasure to announce the general availability of Spring Vault 1.0 – the very first GA release of Spring Vault after almost a year of development.

The artifacts are available from Maven Central and Bintray.

<dependency>
  <groupId>org.springframework.vault</groupId>
  <artifactId>spring-vault-core</artifactId>
  <version>1.0.0.RELEASE</version>
</dependency>

The release ships more than 50 tickets fixed in total. Here’s a very truncated list of the most important features shipping with the release:

• Pluggable application authentication via AppRole, AWS-EC2, client certificates, Cubbyhole (wrapped tokens) and static tokens.
• Support for renewable @VaultPropertySource with credentials rotation.
• Lifecycle-aware session management with token renewal and re-login after terminal token expiry.
• Template API to interact with Vault directly.
• Compatibility with Vault 0.5 to 0.7.
…

On behalf of the community, I am pleased to announce Spring Vault 1.0 RC1.

The artifacts are available in the Milestone repo.

Spring Vault includes 15 fixes, improvements and dependency upgrades.

Here’s a short-list of the most important features shipping with the release:

• Support for renewable @VaultPropertySource with credentials rotation
• Reshaping APIs dropping VaultClient and using RestTemplate instead
• Added EnvironmentVaultConfiguration for simplified configuration without the need to create a derived configuration class.

Contributions

Without the community, we couldn’t be the…

As you probably have seen, we have just announced the GA release of Spring Data release train Ingalls. As the release is packed with way too many features to cover them in a release announcement, I would like to use this post to take a deeper look at the changes and features that come with the 15 modules on the train.

Housekeeping

A very fundamental change in the release train’s dependencies is the upgrade to Spring Framework 4.3 (currently 4.3.6) as the baseline. Other dependency upgrades are mostly driven by major version bumps of the underlying store drivers and implementations that need to…

Last weeks' Spring Data Kay M1 is the first release ever that comes with support for reactive data access. Its initial set of supported stores — MongoDB, Apache Cassandra and Redis — all ship reactive drivers already, which made them very natural candidates for such a prototype. Let’s take a more detailed look at the new programming model and the APIs that make up that support.

Reactive Repositories

The repositories programming model is the most high-level abstraction Spring Data users usually deal with. They’re usually comprised of a set of CRUD methods defined in a Spring Data provided…

On behalf of the community, I am pleased to announce the first milestone releases of Spring Vault and Spring Cloud Vault 1.0.0.M1.

The artifacts are available in the Milestone repo.

What is Spring Vault and Spring Cloud Vault?

Spring Vault is a client for HashiCorp Vault that provides familiar Spring abstractions. It comes with @VaultPropertySource that exposes encrypted properties from Vault the Environment and VaultTemplate to access secrets stored and encrypted inside Vault.

@Configuration
@VaultPropertySource("secret/my-application")
public class AppConfig extends…

In my previous post about Managing Secrets with Vault, I introduced you to Vault and how to store arbitrary secrets using the generic secret backend. Vault can manage more than just secret data like API keys, passwords, and other sensitive string-like data. Today we’re taking a look at Vault’s integration with databases, services, and certificates.

Database credentials tend to be static

When it comes to databases, the regular workflow of getting credentials applying for a database is asking some operator or a self-service tool to give you credentials so your application can log into the…