Performance oriented Spring Data JPA & Hibernate by Maciej Walkowiak

Рет қаралды 21,491

2 ай бұрын

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!

Пікірлер: 38

@vladmihalcea 2 ай бұрын

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 25 күн бұрын

@@frostbittenkingdoms245 Who would have thought? :D

@jonnycoddington1883 2 ай бұрын

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 👌🏻

@lytung1532 Ай бұрын

Thanks for sharing. More sessions like this please!

@JorgeCorradi Ай бұрын

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

@tobyzieglerrr 2 ай бұрын

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!

@user-me3df3xx6l Ай бұрын

This was exceptionally useful, thanks mr. Walkowiak

@rieckpil 2 ай бұрын

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 🍃

@jimishukurow2286 Ай бұрын

Definitely need to try PROJECTIONS ...

@CanhNguyen-ls7kq Ай бұрын

Good talk, thank you Maciej

@praveens2272 2 ай бұрын

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

@SBala-xk6lr Ай бұрын

This was exceptional. Thanks

@ayoubzoubeidi8052 Ай бұрын

thank you for this amazing talk

@fipabrate 2 ай бұрын

Very very good talk. I enjoyed it

@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.

@TheMrDrakiula 2 ай бұрын

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

@joachimdietl6737 Ай бұрын

Nice video!

@odrotbohm 2 ай бұрын

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.

@illyam689 Ай бұрын

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

@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.

@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

@praveens2272 2 ай бұрын

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

@gauntr 2 ай бұрын

Gib code pls 😂

@Arunkumar-uz3vh Ай бұрын

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