Pick the Persistence Model

A new microservice owns one table, notifications, with no relationships to any other table it manages itself. Reads and writes are simple CRUD, and the team wants SQL behaviour that's easy to predict under load. Spring Data JDBC or Spring Data JPA?

See the answer

Spring Data JDBC. There's no relationship depth for a persistence context to manage, no lazy loading worth having, and predictable SQL is an explicit requirement — exactly the profile the comparison card's table points at JDBC for.

Spring Boot
Relational Databases