Spring Data JPA: What is it? And Why Should You Use It?

When you implement a new application, you should focus on the business logic instead of technical complexity and boilerplate code. That’s why the Java Persistence API (JPA) specification and Spring Data JPA are extremely popular. JPA handles most of the complexity of JDBC-based database access and object-relational mappings. On top of that, Spring Data JPA reduces the amount of boilerplate code required by JPA. That makes the implementation of your persistence layer easier and faster.
Sounds great, doesn’t it? It’s no surprise that a lot of development teams use that stack to implement their persistence layer.
Links mentioned in the video-
Getting Started With Hibernate: www.thoughts-o...
What’s the difference between JPA, Hibernate and EclipseLink?: www.thoughts-o...
If you like this video, please give me your thumbs up and share it with your friends and co-workers.
Like my channel? Subscribe!
➜ bit.ly/2cUsid8
Join the free Member Library:
goo.gl/dtyIIC
Read the accompanying post: thoughts-on-ja...
Want to connect with me?
Blog: www.thoughts-on...
Twitter: / thjanssen123
Facebook: / thoughtsonjava
#SpringDataJPA #GettingStarted #Spring

[@techneis]

Bunch of Thanks, Thorben! I appreciate the clarity and precision of the topics.

[@landry_john]

Hi ! Thank you for that clear introduction to Sprind Data JPA. Looking forward to learn a lot about Java Spring Tech.

[@saimyousuf2108]

This guy is criminally underrated.

[@timw594]

I just can't see how these additional layers actually makes things easier especially when stacking other frameworks into the mix like Angular, typescript etc. It just feels like the complexities being added are far worse and introduce excessive moving parts vs just simply learning RDBMS and CRUD operations using JDBC stored procs, SQL etc. Since everything ultimately comes down to the data being stored/accessed by an application and many biz applications are highly customized for the biz, the power that you have within the RDBMS environment to better handle/secure crud operations using standardized pl/sql which is what Spring JPA is going to end up calling anyhow is overwhelming and in more complex implementations will require a developer on the team to learn anyhow to troubleshoot problems. I've been doing full-stack web for decades but the last 15 years have been interesting in regards to how much more complex we've actually made things in the effort to make them easier.

[@Vanuatoo]

In real-life applications you need to have many native queries and standard methods generated by the repository seem like marketing. I try to convince myself that adding another layer on top of JPA brings significant advantage.

[@seeboonsoo]

The best!

[@mithileshtipkari8814]

Excellent explanation, thanks.

[@abedjarjanazy1178]

Outstanding explanation.

[@RanjithKumar-qj9mn]

difference between hibernate sessionfactory and spring data jpa methods (As spring data jpa is an abstraction over JPA and hibernate is the default implementation of spring data jpa)

[@kutilkol]

My jsme ti co nespí, my neznáme spánek. To s čím oni flexí, to my děláme stále. My žijeme Multiverse, jo tady to známe. Toto je náš vesmír, tomu verte páne.

[@francescopaci9435]

can you make a video in MyBatis?

[@surisuri5137]

in real time this is different but nice explain.

[@wilsonmwangi8647]

Good content. Please could you React in your next video. Thanks

[@phash2k]

Thanks Torben, very interesting!

[@gopalaagrawal7414]

Thanks a lot for the explanation

[@krishnaramdas5809]

How to handle if it is a complex query with multiple joins across tables. Can I still use Spring Boot and Repository approach..?

[@monikaveeramalla3381]

Use hibernate sessionfactoy

[@izzyk7905]

Thank you for explanation! I have a question regarding number of levels: I need to have 5-6 levels of depth for subgraphs but it didn't work in hibernate 6.1.6.Final (worked in lower versions though).

[@MarcusHarrise-l9n]

Bashirian Gardens

[@mostinho7]

3:40 spring data JPA features (vs just using entityManager directly) 1. No code repositories 2.

[@alexissuarezalvarez5622]

Hi thanks for the tutorials. I really like Spring data JPA, however I would like to know what happens when we deal with long procedures in the database involving multiple tables. wouldn't that generate very verbose code in our application(repositories, services, etc)?

[@ngn6454]

HI, which repository should we use for Bigquery ?

[@techiesrikanth2447]

Thanks !!

[@vineetpandey3552]

Very nice....

[@MrMikomi]

I get the feeling that this is fine until it isn't ie once your project is no longer simple.

[@darkmesa7933]

absolutely yes....i think plain hibernate JPA offers so much more control over how we can perform complex queries and logic over entities

[@zeemf1]

hi Thorben, is it possible to add the entity graphs to these entity repositories, or should you implement them in a separate parallel layer? As you know this is fine for fast development but the application gets quite slow with many relationship connections. Br,

[@kayladagibbse4617]

Robinson Deborah Anderson Kevin Harris Mark

[@mostinho7]

7:00

[@deepusasidharan2012]

Aha

[@carlosfabio2]

Hey. Thanks for this new and very useful video. Also, I want to say that you speak to fast! Can you speak slowly next time?

[@rosshoyt2030]

you can slow the video with youtube on desktop browser

[@bisikleta1015]

You talk so much about other links and references that it gets tiring

[@danielnoguera2219]

You are a great teacher. Your explanation is simple and deep both. Thanks a lot! Cheers from Argentina!

[@david3979]

What woud you use between `CrudRepository` (seen in th evideo) and `JPARepository` in 2021? Is `JPARepository` just a better version of `CrudRepository` with more automatisation? Also, thank you for the video and the great resources.

[@adamo901]

Thanks a lot for this video. What about the integration with Java EE?

[@sabari.p5048]

Thanks Thorben

[@sydneylawman803]

Wintheiser Garden