@OneToOne relationship in Spring Boot - Performance & Optimization

Performance: @OneToOne relationship

MEDIUM IMPACT

This affects database query performance and page load speed when fetching related entities in a web app.

Fetching related entity data in a @OneToOne relationship

Spring Boot

@OneToOne(fetch = FetchType.LAZY)
private Profile profile;

Lazy fetch loads related entity only when accessed, speeding initial page load and reducing DB load.

📈 Performance GainSpeeds initial load by deferring related data fetch; reduces blocking time by 30-50%

Fetching related entity data in a @OneToOne relationship

Spring Boot

@OneToOne(fetch = FetchType.EAGER)
private Profile profile;

Eager fetch loads related entity immediately, causing slower initial queries and blocking rendering.

📉 Performance CostBlocks rendering until both entities load; can add 1+ seconds delay on slow DB

Performance Comparison

Pattern	DB Queries	Blocking Time	Page Load Impact	Verdict
Eager @OneToOne	1 join or 2 queries immediately	Blocks rendering until complete	Slower LCP, higher initial load	[X] Bad
Lazy @OneToOne	Query only when accessed	Non-blocking initial render	Faster LCP, better user experience	[OK] Good

Rendering Pipeline

When the page requests data, eager @OneToOne triggers a join or extra query before rendering starts, delaying Style Calculation and Paint. Lazy loading defers this until needed, improving initial render.

→Data Fetch

→Style Calculation

→Layout

→Paint

⚠️ BottleneckData Fetch stage due to blocking DB queries

Core Web Vital Affected

LCP

This affects database query performance and page load speed when fetching related entities in a web app.

Optimization Tips

1Use FetchType.LAZY for @OneToOne to avoid blocking initial page load.

2Avoid unnecessary eager fetching to reduce database query time and improve LCP.

3Monitor network requests to detect multiple queries caused by eager loading.

Performance Quiz - 3 Questions

What is the main performance drawback of using FetchType.EAGER in a @OneToOne relationship?

A It increases CSS selector complexity

B It causes layout shifts during page scroll

C It delays initial page rendering by loading related data immediately

D It reduces bundle size

DevTools: Network

How to check: Open DevTools > Network tab, reload page, watch for multiple DB API calls or delayed responses before main content loads.

What to look for: Look for blocking API calls delaying main content; multiple sequential queries indicate eager loading impact.

Practice

1. What does the @OneToOne annotation represent in Spring Boot JPA?

easy

A. A relationship where one entity is linked to exactly one other entity

B. A relationship where one entity is linked to many entities

C. A relationship where many entities are linked to many entities

D. A relationship where entities are not linked at all

Solution

1. Step 1: Understand the meaning of @OneToOne

   The @OneToOne annotation defines a direct one-to-one link between two entities in JPA.

2. Step 2: Compare with other relationship types

   Unlike @OneToMany or @ManyToMany, @OneToOne means exactly one entity matches exactly one other entity.

3. Final Answer:

   A relationship where one entity is linked to exactly one other entity -> Option A

4. Quick Check:

   @OneToOne = one-to-one link [OK]

Hint: One entity matches exactly one other entity [OK]

Common Mistakes:

• Confusing @OneToOne with @OneToMany
• Thinking it allows multiple linked entities
• Ignoring the uniqueness of the relationship

2. Which annotation is used on the owning side of a @OneToOne relationship to specify the foreign key column?

easy

A. @MappedBy

B. @Column

C. @JoinColumn

D. @Entity

Solution

1. Step 1: Identify the owning side annotation

   The owning side uses @JoinColumn to specify the foreign key column in the database.

2. Step 2: Differentiate from mappedBy

   @MappedBy is used on the inverse side, not the owning side.

3. Final Answer:

   @JoinColumn -> Option C

4. Quick Check:

   Owning side uses @JoinColumn [OK]

Hint: Owning side uses @JoinColumn for foreign key [OK]

Common Mistakes:

• Using @MappedBy on owning side
• Confusing @Column with @JoinColumn
• Forgetting to specify @JoinColumn

3. Given the following code snippet, what will be the output when fetching Person and accessing person.getPassport().getNumber()?

@Entity
class Person {
  @Id
  private Long id;

  @OneToOne
  @JoinColumn(name = "passport_id")
  private Passport passport;

  // getters and setters
}

@Entity
class Passport {
  @Id
  private Long id;
  private String number;

  // getters and setters
}

medium

A. Throws NullPointerException because passport is not initialized

B. Returns the passport number linked to the person

C. Returns null because @OneToOne is missing mappedBy

D. Compilation error due to missing @MappedBy

Solution

1. Step 1: Analyze the @OneToOne mapping

   The Person entity owns the relationship with @JoinColumn, so passport is linked properly.

2. Step 2: Understand the data fetching

   When fetching Person, accessing person.getPassport().getNumber() returns the linked Passport's number if data exists.

3. Final Answer:

   Returns the passport number linked to the person -> Option B

4. Quick Check:

   Proper @OneToOne with @JoinColumn returns linked entity [OK]

Hint: Owning side with @JoinColumn returns linked entity [OK]

Common Mistakes:

• Assuming mappedBy is required on owning side
• Expecting NullPointerException without data check
• Confusing compilation errors with runtime behavior

4. Identify the error in this @OneToOne mapping:

@Entity
class User {
  @Id
  private Long id;

  @OneToOne(mappedBy = "user")
  private Profile profile;
}

@Entity
class Profile {
  @Id
  private Long id;

  @OneToOne
  private User user;
}

medium

A. Missing @JoinColumn on Profile entity owning side

B. mappedBy should be on Profile, not User

C. User entity should not have @OneToOne annotation

D. Profile entity must use mappedBy instead of @OneToOne

Solution

1. Step 1: Check owning side annotations

   Profile is the owning side but lacks @JoinColumn to specify the foreign key.

2. Step 2: Understand mappedBy usage

   mappedBy is correctly on User side, indicating inverse side.

3. Final Answer:

   Missing @JoinColumn on Profile entity owning side -> Option A

4. Quick Check:

   Owning side needs @JoinColumn [OK]

Hint: Owning side must have @JoinColumn [OK]

Common Mistakes:

• Placing mappedBy on owning side
• Omitting @JoinColumn on owning side
• Confusing owning and inverse sides

5. You want to create a bidirectional @OneToOne relationship between Employee and Desk. Which is the correct way to define the relationship so that Employee owns the relationship and the foreign key is in the Desk table?

hard

A. In Employee: @OneToOne(mappedBy = "desk") Desk desk; In Desk: @OneToOne @JoinColumn Employee employee;

B. In Employee: @OneToOne @JoinColumn Desk desk; In Desk: @OneToOne(mappedBy = "desk") Employee employee;

C. ;eeyolpme eeyolpmE nmuloCnioJ@ enOoTenO@ :kseD nI ;ksed kseD )"eeyolpme" = yBdeppam(enOoTenO@ :eeyolpmE nI

D. In Employee: @OneToOne(mappedBy = "employee") Desk desk; In Desk: @OneToOne @JoinColumn Employee employee;

Solution

1. Step 1: Determine owning side and foreign key location

   The foreign key is in Desk table, so Desk owns the relationship.

2. Step 2: Correct annotation placement

   Desk must have @JoinColumn and no mappedBy; Employee uses mappedBy to point to Desk's field.

3. Step 3: Match option with correct annotations

   In Employee: @OneToOne(mappedBy = "employee") Desk desk; In Desk: @OneToOne @JoinColumn Employee employee; matches this.

4. Final Answer:

   In Employee: @OneToOne(mappedBy = "employee") Desk desk; In Desk: @OneToOne @JoinColumn Employee employee; -> Option D

5. Quick Check:

   Foreign key side owns with @JoinColumn, other side uses mappedBy [OK]

Hint: Foreign key side owns with @JoinColumn, other side uses mappedBy [OK]

Common Mistakes:

• Assigning owning side incorrectly
• Placing mappedBy on owning side
• Confusing which table holds foreign key