Performance oriented Spring Data JPA & Hibernate by Maciej Walkowiak

Hibernate - the most popular persistence technology for Java - also the most controversial one. Some people love it, some people hate it. No matter in which group you are, the chances you will work in Hibernate in at least one project are close to 100% - and you have no other choice than learning it. Not only the basics, but most importantly - how to leverage the power of Hibernate without sacrificing application and database performance.
In this session you will learn how to configure Hibernate and Spring Data JPA for efficient database connection management, what is a N+1 problem and how to solve it, how and when to use projections for fast data retrieval ... and more!

[@vladmihalcea]

Great talk and thanks for the shout out!

[@richardwang3438]

you look familiar

[@frostbittenkingdoms245]

Of course you were mentioned in the first five minutes :D.

[@vladmihalcea]

@@frostbittenkingdoms245 Who would have thought? :D

[@jonnycoddington1883]

This is an absolute goldmine, thanks Maciej!!! We have a part of our application that takes about 40ms to do a simple insert so this talk is excellently timed 👌🏻

[@rieckpil]

Awesome talk, Maciej. One can not emphasis enough the importance of understanding what's going on behind Hibernate & Spring Data JPA - I really liked the wallpaper 🍃

[@lytung1532]

Thanks for sharing. More sessions like this please!

[@jimishukurow2286]

Definitely need to try PROJECTIONS ...

[@user-me3df3xx6l]

This was exceptionally useful, thanks mr. Walkowiak

[@JorgeCorradi]

Pure gold! Thank you so much for the awesome presentation.

[@tobyzieglerrr]

Very very good talk, hands on and i took away at least 4 things that i did not know or did not fully understand before. Thanks!

[@CanhNguyen-ls7kq]

Good talk, thank you Maciej

[@SBala-xk6lr]

This was exceptional. Thanks

[@fipabrate]

Very very good talk. I enjoyed it

[@ayoubzoubeidi8052]

thank you for this amazing talk

[@praveens2272]

If anyone doesn't understand jpa and hibernate at this level(internal workings), they will screw up the application. I think it's better to write plain SQL queries and execute or may be JOOQ helpful.

[@rajeshhazari]

Thanks, do you have any simple spring boot starter for Jooq for and intermediate level experience with jdbc and pure sql

[@praveens2272]

@@rajeshhazari i didn't understand your question, you need code samples for JOOQ ?

[@rajeshhazari]

​@@praveens2272 yes some samples starters using jooq to show complex examples

[@tahahajivand1843]

it was really helpful. thank you for your hard work

[@joachimdietl6737]

I once attended one of Vlad's lectures at the JAX and i had the feeling (same as here) that the time is over, when it is getting interesting.

[@joachimdietl6737]

Nice video!

[@illyam689]

34:34 "It's a commercial tool, which is great.. for Vlad" ROTFL!! 🤣🤣🤣

[@TheMrDrakiula]

Vlad actually used to work on the Hibernate project for RedHat in the past at some point.

[@odrotbohm]

Is there any reason you did not fix the aggregate model instead? It's a phenomenon I run into quite frequently: folks run into performance problems and immediately resort to tweaking persistence metadata, when *actually* the problem is in the model itself.
Spring Data deals with DDD aggregates, in which Many-to-One relationships to other aggregates have no place at all. Those would be modeled as identifier references instead, so that these are basic values to Hibernate, and it would not need to resolve references The entire lazy/eager discussion is avoided on the Hibernate level. No get-by-reference tricks, no tweaking of Hibernate metadata. Applications would simply resolve the identifiers when they *actually* need the reference. Creating a BankTransfer wouldn't even need to resolve the accounts beforehand.

[@vivekbansal-bc9eg]

I have a question in bank transfer execute method he said hibernate will open the session then closes in case of findById.But earlier he said because of OSIV it mantains a session throughout request after a db call. can anyone answer

[@kavinduchamiran4869]

27:20 I didn't understand how annotating the execute() method with @Transactional reduced the number of database queries. Can someone explain pls?

[@TheMaciejek]

Because we have already assigned ids for these entities, and thus save() method will underneath invoke merge() instead of persist() and merge underneath has to check if these entities exists, so it has to issue another select query. In case when you are using @Transactional, the entities from the first and second select will be stored in hibernate session cache and thus the merge, instead of firing new request, can simply take it from cache.

[@kanaillaurent526]

First YAGNI Spring

[@nirmalmewada]

Simple answer is dont use Hibernate, It makes simple problem more simpler (which we might not need) and complex problem more complex (which we definatly not need it), Got for micro framework like MyBatis if you really want to consider performance, its great sweet point.

[@Sucheit]

cant even lazy load one to one

[@praveens2272]

This demo code is available in GitHub? If not please share the link. Thanks.

[@gauntr]

Gib code pls 😂

[@Arunkumar-uz3vh]

It's there on his GitHub page. Repo name: performance-oriented-spring-data-jpa-talk

[@matdryz]

Do you have a long running transaction? just split it into two transactions 😂

[@abirbasak1948]

Using hibernate for 5 years, I agree that it is not the best tool for database handling. Most of the time plain SQL is much more predictable and easy to work with

[@geraldodev]

Or use SQL and clojure with it's awesome data strucutres :)

[@jimishukurow2286]

Projections with nested entities are sucks ...