Moderate JPA Question 131 of 226

How do you fix N+1 without turning everything into EAGER?

Java Specialist · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DATABASE INDEX

Without indexScan every row

With indexJump to keys

CostWrites slower

Simple meaning

Use JOIN FETCH in a dedicated query, an @EntityGraph on that use case, or a DTO projection that joins in SQL.

WHY — JPA instead of guessing?

Why interviewers care about JPA:

This is a process

question about JPA.

Panels listen for order,

trade-offs, and what you would actually do on a Backend project - not buzzwords.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
Use JOIN FETCH in
a dedicated query, an @EntityGraph on that use case, or a DTO projection that joins in SQL.
2
Batch fetching with @BatchSize
reduces the N but does not make it one query.
3
Never globally EAGER a
OneToMany to hide N+1.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“Batch fetching with @BatchSize reduces the N but does not make it one query.”

Break into beats

BatchfetchingwithBatchSizereducesthe

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

Use JOIN FETCH in a dedicated query, an @EntityGraph on that use case, or a DTO projection that joins in SQL. Batch fetching with @BatchSize reduces the N but does not make it one query.