Spring & Spring Data JPA: Managing Transactions

Best video about this subject! Thanks so much!!

Thank you, beneficial video!

Thank you for another great video . Can you also cover the need of optimistic locking and when do we need to use that in spring data jpa .

Thank you, a very clear video, just a question: does spring support both declarative and programmatic transaction management ?

Commenting only to appreciate how well you have organized this video.

Thank so much!, I have a question, what happen if I have a springboot app to read/write on database without @Transactional annotations and another springboot app that process data and call to that app to write data? (and this service effectively has the @Transactional annotation), if an exception occurs, there will be a roll-back or not?, @Transactional its necessary in both services?, or only in the service connected to database?

Excellent video, please could you talk about Hibernate caching? thanks...

Thanks for the video. It helped me a lot to understand more about Phanton Read and how to deal with it.

Been struggling for a few days to figure out how this annotations help with our backend applications and your video made it so clear to me now. God bless you,man!

Sometimes the rollback for Exception.class won't work when we use multiple entities for multiple tables and make more than one CRUD operations in a service class . Any suggestions for this .. ??

Thanks for the great video. If there are 3 different table updates. I have written them in different methods. I used @Transaction annotation for all of them but when 3rd fails, it does not rollback 1st two method transactions. How can I solve this?

Very clear explanation! Thank you!

didn't know that readonly done by not doing dirty checking! thanks

Gave me very good clear knowledge on @Transactional attribute. Thank you.

your course is very clear I like it

good explanation, thank you for the video

My transaction executes an update statement even tho i did not explicitly call it. Why does this happen when transaction is about to end. Im confused help

I tend to feel - companies promoted hibernate because they wanted developers to spend their entire life learning it so that companies dont have to pay developers what they should - which is custom written JDBC code, a developer is not paid to study for years a complex and changing framework like hibernate and this effort is tremendous - hibernate has features and until reader find good videos and reads like you they will keep ending up using such framework incorrectly and also failing interviews a lot more - until a framework provides correct and effectively detailed documentation - its a curse to technical community - spring is no exception to this rule. Configuration heavy development is good for companies who dont have to pay what they should to technical people like us and they force us to spend our entire life reading and learning so called ready to use building blocks such as annotations and frameworks such as spring boot and hibernate - its a curse - think to yourself what I just said. Although I can't undermine your effort sharing your hard earned knowledge here Thorben, I just wanted to provided the insight of what we dont look at, why do we have to create such curse in name of innovation.

misuse of phrase "extremely simple" - in the first line of this video - I really feel BMT is the way to go - so many features offered in hibernate are just so complex and only apply to very specific situation - hibernate is undesirable if you ask me - for what it offers at the cost it offers.

Thank you for another great explanation. By the way why didn't you mention 'isolation' attribute?

So @ Transactional is not required in spring boot ?

Hi janssen,

Thanks for excellently explaining transaction management in Spring Data JPA.
Is there any resource on your blog expalining the use of @Lock and @Version please?

Regads

Thank you for your great work

kya hal chal bhai

Very informative and well explained. Thank you!

Sir your video are very informative..but one question arises,How to avoid cocurrent read and insert if your java application is deployed on different servers Or jvm and connect with one db how transaction work in that scenario..

Great work. Keep going ..

Great video Thorben, thank you!

Nice 👍

It is possible to add the annotation @Transactional on the class. On each of my services I put on the class level @Transactional(readOnly = true) like that by default I do not open a transaction and if my method modify the base then I add an @Transactional on the méthode.

Thanks for sharing all this knowledge. I m confused on why we need to add @Transaction without customizing it in the service if it's by default in repository.

Top tier content, thank you for your work.

excellently explained ee+, Please make more videos on this.