Join fetch for optimization in Spring Boot - Performance & Optimization

Performance: Join fetch for optimization

HIGH IMPACT

This affects the database query performance and the time it takes to load related data in the application, impacting page load speed and responsiveness.

Loading an entity with its related entities efficiently

Spring Boot

List<Order> orders = entityManager.createQuery("SELECT o FROM Order o JOIN FETCH o.items", Order.class).getResultList();

This fetches orders and their items in a single query, reducing database calls.

📈 Performance GainSingle query reduces database round-trips, improving load speed and reducing LCP

Loading an entity with its related entities efficiently

Spring Boot

List<Order> orders = entityManager.createQuery("SELECT o FROM Order o", Order.class).getResultList();
for (Order order : orders) {
  order.getItems().size(); // triggers separate query per order
}

This triggers N+1 queries: one for orders and one for each order's items, causing many database round-trips.

📉 Performance CostTriggers N+1 queries causing multiple database round-trips and slower page load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Without join fetch (N+1 queries)	N+1 database queries	Multiple server response delays	Slower initial paint due to delayed data	[X] Bad
With join fetch (single query)	Single database query	Faster server response	Faster initial paint with data ready	[OK] Good

Rendering Pipeline

Join fetch optimizes data retrieval by reducing database queries, which speeds up server response and reduces time before content is sent to the browser.

→Data Fetching

→Server Response

→Rendering

⚠️ BottleneckDatabase query count and latency

Core Web Vital Affected

LCP

This affects the database query performance and the time it takes to load related data in the application, impacting page load speed and responsiveness.

Optimization Tips

1Use join fetch to load related entities in one database query.

2Avoid triggering multiple queries for related data (N+1 problem).

3Fewer database queries lead to faster server response and better LCP.

Performance Quiz - 3 Questions

What is the main performance benefit of using join fetch in Spring Boot?

A It caches all data on the client side to avoid server calls.

B It reduces the number of database queries by fetching related entities in one query.

C It delays data loading until user interaction.

D It compresses the data sent over the network.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and observe the number of API/database calls made to fetch data.

What to look for: Fewer and faster API calls indicate good join fetch usage; many repeated calls indicate N+1 problem.

Practice

1. What is the main purpose of using JOIN FETCH in Spring Boot JPA queries?

easy

A. To create a new table for the joined entities

B. To delete related entities automatically when the parent is deleted

C. To load related entities eagerly in a single query and avoid multiple database hits

D. To update related entities in batch

Solution

1. Step 1: Understand what JOIN FETCH does

   JOIN FETCH tells JPA to load related entities eagerly in the same query instead of lazy loading them later.

2. Step 2: Recognize the performance benefit

   This reduces the number of database queries, improving performance by avoiding the N+1 select problem.

3. Final Answer:

   To load related entities eagerly in a single query and avoid multiple database hits -> Option C

4. Quick Check:

   Join fetch = eager load related data [OK]

Hint: Join fetch loads related data in one query to boost speed [OK]

Common Mistakes:

• Thinking join fetch deletes or updates data
• Confusing join fetch with creating new tables
• Assuming join fetch delays loading entities

2. Which of the following is the correct JPQL syntax to fetch a parent entity and its child entities using join fetch?

easy

A. SELECT p FROM Parent p JOIN FETCH p.children

B. SELECT p FROM Parent p JOIN p.children FETCH

C. SELECT p FROM Parent p FETCH JOIN p.children

D. SELECT p FROM Parent p LEFT JOIN p.children FETCH

Solution

1. Step 1: Recall correct JPQL join fetch syntax

   The correct syntax places JOIN FETCH before the association path: JOIN FETCH p.children.

2. Step 2: Check each option

   Only SELECT p FROM Parent p JOIN FETCH p.children matches the correct syntax. The others misuse the order of keywords or use incorrect join types.

3. Final Answer:

   SELECT p FROM Parent p JOIN FETCH p.children -> Option A

4. Quick Check:

   Join fetch syntax = JOIN FETCH association [OK]

Hint: Remember: 'JOIN FETCH' comes together before the association [OK]

Common Mistakes:

• Swapping FETCH and JOIN keywords
• Placing FETCH after the association path
• Using FETCH without JOIN keyword

3. Given the following JPQL query:

SELECT o FROM Order o JOIN FETCH o.items WHERE o.id = :id

What will happen when this query runs?

medium

A. It loads only the items without the Order

B. It loads the Order and all its items in one query, avoiding lazy loading

C. It throws a syntax error because JOIN FETCH cannot be used with WHERE

D. It loads only the Order, items are loaded lazily later

Solution

1. Step 1: Analyze the query structure

   The query uses JOIN FETCH to eagerly load the items collection along with the Order entity filtered by id.

2. Step 2: Understand the effect of join fetch with WHERE

   The WHERE clause filters the order, but the join fetch still loads the items eagerly in the same query.

3. Final Answer:

   It loads the Order and all its items in one query, avoiding lazy loading -> Option B

4. Quick Check:

   Join fetch + WHERE = eager load filtered data [OK]

Hint: Join fetch loads related data even with WHERE filters [OK]

Common Mistakes:

• Thinking join fetch causes syntax errors with WHERE
• Assuming items load lazily despite join fetch
• Confusing join fetch with separate queries

4. Consider this JPQL query:

SELECT c FROM Customer c JOIN FETCH c.orders o WHERE o.status = 'PENDING'

What is the likely problem with this query?

medium

A. It may return duplicate Customer entities due to multiple matching orders

B. It will fail because JOIN FETCH cannot have an alias

C. It will not fetch orders eagerly because of the WHERE clause

D. It will only fetch orders with status other than 'PENDING'

Solution

1. Step 1: Understand join fetch with filtering on collection

   Filtering on orders with WHERE o.status = 'PENDING' can cause multiple rows per customer if they have multiple pending orders.

2. Step 2: Recognize duplicate root entities issue

   This leads to duplicate Customer entities in the result list unless distinct is used.

3. Final Answer:

   It may return duplicate Customer entities due to multiple matching orders -> Option A

4. Quick Check:

   Join fetch + filtered collection = possible duplicates [OK]

Hint: Filtering join fetch collections can cause duplicates [OK]

Common Mistakes:

• Believing join fetch cannot have aliases
• Thinking WHERE disables eager loading
• Assuming only non-matching orders are fetched

5. You want to optimize loading a list of Author entities with their books and each book's publisher in one query. Which JPQL query correctly uses join fetch for this?

hard

A. SELECT a FROM Author a JOIN FETCH a.books, b.publisher

B. SELECT a FROM Author a JOIN a.books b JOIN FETCH b.publisher

C. SELECT a FROM Author a JOIN FETCH a.books JOIN b.publisher

D. SELECT a FROM Author a JOIN FETCH a.books b JOIN FETCH b.publisher

Solution

1. Step 1: Identify the need for nested join fetch

   To load authors with books and each book's publisher eagerly, use join fetch on both associations.

2. Step 2: Check the syntax for multiple join fetches

   SELECT a FROM Author a JOIN FETCH a.books b JOIN FETCH b.publisher correctly uses JOIN FETCH a.books b and then JOIN FETCH b.publisher to fetch nested associations.

3. Final Answer:

   SELECT a FROM Author a JOIN FETCH a.books b JOIN FETCH b.publisher -> Option D

4. Quick Check:

   Multiple join fetches = eager load nested relations [OK]

Hint: Use multiple JOIN FETCH for nested eager loading [OK]

Common Mistakes:

• Missing JOIN FETCH on nested association
• Using JOIN without FETCH for nested entities
• Incorrect syntax with commas or missing aliases