The amount of data collected by applications nowadays is growing rapidly. Many of them need to support both relational SQL and non-relational NoSQL databases. Jakarta Data provides an API to allow easy data access. Developers can split the persistence mechanism and the model using common features like the Repository pattern and seamlessly switch between SQL and NoSQL databases or even use both in the same application.
First we'll compare popular Java data access frameworks for SQL/JPA and NoSQL databases. We are going to look at Jakarta NoSQL/JNOSQL, Spring Data, Micronaut Data, Quarkus/Panache or DeltaSpike Data. What do they have in common? How do they compare, what are the differences and similarities? We'll show each of them with a selection of different NoSQL or SQL databases to learn how they work and what concepts like CRUD operations, the Repository pattern, pagination or sorting they support.
Followed by an overview of Jakarta Data and how it can help migrate your data applications to a vendor-neutral future, becoming greater than the sum of all existing solutions.
