Build faster persistence layers with Spring Data JPA 3 by Thorben Janssen @ Spring I/O 2024

Spring I/O 2024 - 30-31 May, Barcelona

Over the years, Spring Data JPA has become the de facto standard for persisting data in a relational database. It provides excellent developer productivity and is so easy to use that you can learn it within a few hours. And Spring Data JPA 3 improves all of that even further.

But handling vast amounts of data or guaranteeing very short response times still causes many problems. Features and concepts that work perfectly fine for smaller applications start to slow down your application.

The good news is that you can easily avoid all of this. Spring Data JPA is a great fit for complex projects with high-performance requirements. You only need to know which features to use and which to avoid.

During this talk, I’ll show you how to get the most out of your persistence layer and which new features in Spring Data JPA 3 help you improve your application’s performance even further.

[avalagum]

That hibernate session metrics are very useful.
This talk is very good.

[jesprotech]

That part about the interface projections is very very interesting. Great session and really worth watching if one is used to working with the JPA. Especially when finding limitations to what we are doing.

[sagarrout]

Hi @Thorben, Thanks for the session. It was quite insightful.

[ferlezcano]

Thorben must wear his white t-shirt + sky blue shirt whenever he talks about Hibernate.

Excellent content as always, by the way. I have learnt so much with him over the years 💪

[linhvudev]

Thank you for your talk! As usual, it convinced me get rid of JPA/Hibernate again and again. After every talk about JPA, I hate my laziness because of not switching to another, I realize I only use JPA for 'create' because I'm lazy at making a insert statement at the beginning, for others like 'update', 'delete', and especially 'read', I always have to use specific @Query instead to bypass JPA drawbacks.

[yadigarcaliskan]

All those recommendations are clear to everyone who has two years of programming experience

[pnmjzjn]

31:38 In what cases do you use interface in projections?
What are the advantages over dto, record?

[Mrhennayo]

Frankly I will use jpa as simple selects for smaller projects elsewhere pure jdbc does the job or plsql

[blonditbg]

My recommendation would be to not use JPA at all, the fact that you need to know all that stuff to not hurt yourself due to incorrect framework usage (not even talking about DB performance issues) looks like a bad thing to begin with. Simpler tools like jooq seem to be better ?

[mmo]

Give me one reason ( besides query+ db ) to use jpa. Im just asking