Lazy versus eager fetching: what is the safe default?
PICTURE THIS: SQL JOIN
Simple meaning
Lazy is the safe default for associations so you do not pull an entire object graph on every find.
WHY — JPA instead of guessing?
Why interviewers care about JPA:
contrast on JPA, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
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:
- 1Lazy is the safe
default for associations so you do not pull an entire object graph on every find.
- 2Eager always joins or
selects related rows, which is fine for a tiny mandatory relation and deadly for collections.
- 3If you know you
need children, fetch them explicitly with a join fetch query or an entity graph.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Lazy is the safe default for associations so you do not pull an entire object graph on every find. Eager always joins or selects related rows, which is fine for a tiny mandatory relation and deadly for collections.