Hibernate N+1 problem and solution | Hibernate Interview Questions and Answers | Code Decode

In this video of n+1 problem in code decode we have explained about the what the problem is all about and how to solve this problem.
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
openinapp.co/u...
Course Description Video :
yt.openinapp.c...
Referral Code : Cod3095
Playstore link nxtlvl.in/2xa
App Store Link nxtlvl.in/xft
What is Hibernate N+1 Select Problem
The N + 1 Select problem is a performance issue in Hibernate. In this problem, a Java application makes N + 1 database calls (N = number of child objects fetched). For example, if N= 2, the application makes 3 (N+1= 3) database calls.
Example - Employees and Departments have Many To one relationship . One Department ( Parent ) can have multiple Employees (Child)
// Unidirectional mapping . By default its lazy
Using
@OneToMany(fetch = FetchType.LAZY)
@JoinColumn(name="Dept_id") // dept_id will be column in Employee table.
Now we need to fetch all departments ,
What all steps will be done now to fetch all departments -
by default its lazy so first a call goes to Department table and fetch all departments (only id and name - No employes list fetched)
Then while returning, for each department now a call goes to fetch list of employees. So N calls goes now, each for 1 department.
What is Hibernate N+1 Select Problem’s Solution
At SQL level, what ORM needs to achieve to avoid N+1 is to fire a query that joins the two tables and get the combined results in single query.
Spring Data JPA Approach-
using left join fetch, we resolve the N+1 problem
using attributePaths, Spring Data JPA avoids N+1 problem
Hibernate Approach
Using HQL Query - "from Department d join fetch d.listOfEmployees Employee e”
Criteria criteria = session.createCriteria(Department.class);
criteria.setFetchMode("listOfEmployees", FetchMode.EAGER);
.
What is @EntityGraph(attributePaths = {"listOfEmployees"})
At SQL level, what ORM needs to achieve to avoid N+1 is to fire a query that joins the two tables and get the combined results in single query.
Spring Data JPA Approach-
using left join fetch, - we can use JOIN FETCH. The FETCH keyword of the JOIN FETCH statement is JPA-specific. It instructs the persistence provider to not only join the two database tables contained in the query, but also initialize the association on the returned entity. It works with both JOIN and LEFT JOIN statements.
using attributePaths, - EntityGraphs are introduced in JPA 2.1 and used to allow partial or specified fetching of objects. When an entity has references to other entities we can specify a fetch plan by EntityGraphs in order to determine which fields or properties should be fetched together.
What is @EntityGraph(attributePaths = {"listOfEmployees"})
Hibernate Approach
Using HQL Query - "from Department d join fetch d.listOfEmployees Employee e”
Using Criteria
Criteria criteria = session.createCriteria(Department.class);
criteria.setFetchMode("listOfEmployees", FetchMode.EAGER);
Most Asked Core Java Interview Questions and Answers: • Core Java frequently a...
Advance Java Interview Questions and Answers: • Advance Java Interview...
Java 8 Interview Questions and Answers: • Java 8 Interview Quest...
Hibernate Interview Questions and Answers:
• Hibernate Interview Qu...
Spring Boot Interview Questions and Answers:
• Advance Java Interview...
Angular Playlist: • Angular Course Introdu...
SQL Playlist: • SQL Interview Question...
GIT: • GIT
Subscriber and Follow Code Decode
Subscriber Code Decode: www.youtube.co...
LinkedIn : / codedecodeyoutube
Instagram: / codedecode25
#N+1problem #hibernate #codedecode

[@chetankhandave1072]

You are one of the best teacher I have ever seen. Your explanation in such simple language shows your thorough study. Thanks for the video and Best of luck.

[@CodeDecode]

Thanks a lot Chetan 🙂🙂👍

[@nidatariq6992]

Excellent Explanation

[@CodeDecode]

Thanks

[@arunr8764]

The best explanation I have seen for n+1 problem...

[@CodeDecode]

Thanks Arun

[@vikaskollu]

Thank You. Very Good Explanation.

[@CodeDecode]

You are welcome!

[@srisureshshetty]

Very good explanation. Thanks for the tutorial.

[@rajat_singla]

Great explanation. Would be great if you can explain join fetch and entity graphs in detail as you mentioned towards the end of the video. Thanks.

[@CodeDecode]

Sure we will do that Rajat🙂👍

[@ChristForAll-143]

@Rajat singla dude its just sql left join there is nothing special and they are just implementing it via hibernate and spring data dpa - at the end its just left join

[@gopishettymahindra2713]

Great Explanation . The Best Explanation I have seen for N+1 Problem

[@CodeDecode]

Thanks 😊

[@samuelr-t4d]

thanks for your explanation. This is one of the important interview quuestion

[@CodeDecode]

Thanks 👍

[@48mantusubudhi72]

if we are using fetchType as Eager then the N+1 problem should be fixed right . at the end we are dealing with object creation of realted tables .why do we need so much complications then ?

[@CodeDecode]

Performance is the reason people in It world moves towards lazy loading.

[@vipulrohilla1383]

Great explanation!!

[@CodeDecode]

Thanks

[@ayushjain7555]

Thanks for this explanation one question if I set fetch type as eager then will this problem arise?

[@theprofessor252]

Looking forward to the next video on this.

[@CodeDecode]

Sure Karthik 👍

[@abhilashchaparala7651]

Great explanation. If possible could you please explain entity graphs in detail. Thanks for the video

[@CodeDecode]

Sure 👍Noted 🙂

[@ahmedelsabagh6990]

Excellent tutorial!

[@CodeDecode]

Thanks

[@sureshmanne7245]

how is the {"listOfEmployees"} referred to Employee table?

[@CodeDecode]

List of employees is actually a list employee entity. Entity maps to relational table. Employee is actually a table in sql

[@18ajai]

Why can't we just use Eager fetch in such scenarios?

[@AshishSingh-rx4sq]

Super demonstration.

[@CodeDecode]

Thanks Ashish 😇👍👍

[@dmytro4312]

very cool and usefull video, thanks a lot)

[@CodeDecode]

🙂🙂👍👍

[@anurani7084]

Great explanation..pls do a video on entity graph

[@CodeDecode]

Sure Anu👍🙂

[@luka.nguyen7]

@Code Decode: I have a question that which is the best-practice to solve N+1 problem, is it entity graph?

[@phanimc11211]

please explain entity graphs in detail. Thanks for the video

[@sandysworld7529]

Great explanation.. pls do explain JOIN FETCH and entity graph as well.

[@CodeDecode]

sure we will cover it soon

[@shubhamsamdani3503]

Thanks for this one. please prepare one video for entity graph.

[@CodeDecode]

sure shubham we will upload it soon

[@syedfaizan5841]

where is the transaction video after propogation i mean you told you will cover transaction isolation

[@sahilpatil1111]

Thanks, this issue asked multiple times in interview but i have not answered 😑 Pls help in best way to fetch result in custom dto after join non relationship table

[@CodeDecode]

No problem Sahil. Now you know it👍. Sure we will create videos on views and custom dtos 👍

[@komal_yadav]

Please tell more on entitygraph

[@CodeDecode]

Sure Komal 👍👍

[@rohitbagdi5155]

Can I just add fetch type as eager in the entity class and will it do the same ?

[@CodeDecode]

Yepp Rohit

[@syedfaizan5841]

thanks but please transaction isolation

[@tannubajpai4782]

Thnx u ma'am

[@CodeDecode]

Thanks Tannu🙂👍

[@amittripathy-kl1cw]

is there any code respository for this code?

[@Hiteshdua-o6b]

solution start @10:00 min

[@ramprasath4788]

Good

[@CodeDecode]

Thanks

[@satya-b4n]

if we use EAGER instead FETCH in @onetomany annotation will it solve the problem?