Jakarta Data. What Does It Mean for Java Community?

A while ago, a new specification regarding data access arose — Jakarta Data. As it is inferred from the name, this specification is a part of the Jakarta EE project. From the first glance, who cares, except for the fact that Hibernate decided, that from now on it implements two specifications — Jakarta Persistence API (aka JPA) and Jakarta Data. We, as developers, tend to work with Hibernate via Spring Data, which suddenly has some problems when working with Jakarta Data. So, what does that mean?

This talk tries to bridge this gap and explain what will happen next and how we as developers are supposed to live with this. We'll discuss in details why Spring Data is not capable to implement Jakarta Data itself, and what we can do if we still would want to work with Jakarta Data implementations in Spring projects.