@techneis

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

@danielnoguera2219

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

@saimyousuf2108

This guy is criminally underrated.

@landry_john

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

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

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

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

@nwobodogeorge5370

This is the best video ever on spring data jpa, & 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.

@mostinho7

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

@CodeJava

well explanation from expert. Kudos!

@krishnaramdas5809

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

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

@seeboonsoo

The best!

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

@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)?

@surisuri5137

in real time this is different but nice explain.

@abedjarjanazy1178

Outstanding explanation.

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

@MrMikomi

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