@Id and @GeneratedValue for primary keys in Spring Boot - Performance & Optimization

Performance: @Id and @GeneratedValue for primary keys

MEDIUM IMPACT

This affects database interaction speed and server response time during entity creation.

Defining primary keys for database entities

Spring Boot

@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

Database auto-generates unique IDs, reducing server-side checks and speeding inserts.

📈 Performance Gainreduces insert latency by avoiding manual ID management

Defining primary keys for database entities

Spring Boot

@Id
private Long id; // manually assigned IDs in code

Manually assigning IDs can cause conflicts and requires extra database checks, slowing inserts.

📉 Performance Costadds latency due to extra DB queries for uniqueness checks

Performance Comparison

Pattern	DB Queries	Locking	Insert Latency	Verdict
Manual ID assignment	Extra uniqueness checks	None	High due to checks	[X] Bad
@GeneratedValue TABLE	Additional query per insert	Possible lock contention	Medium	[!] OK
@GeneratedValue IDENTITY	Single insert query	No extra locking	Low	[OK] Good

Rendering Pipeline

When saving an entity, the ORM uses @Id and @GeneratedValue to assign a primary key before insert. The chosen strategy affects how many database queries and locks occur.

→Database Insert

→Transaction Management

⚠️ BottleneckExtra queries or locks for ID generation increase insert latency.

Optimization Tips

1Prefer GenerationType.IDENTITY for minimal insert overhead.

2Avoid manual ID assignment to prevent extra uniqueness checks.

3Avoid GenerationType.TABLE due to extra queries and locking.

Performance Quiz - 3 Questions

Which @GeneratedValue strategy typically causes the least database overhead during inserts?

A GenerationType.TABLE

B GenerationType.IDENTITY

C Manual ID assignment

D GenerationType.SEQUENCE with no caching

DevTools: Database Profiler or SQL Log

How to check: Enable SQL logging in Spring Boot, perform inserts, and observe queries generated for ID assignment.

What to look for: Look for extra SELECT or UPDATE queries related to ID generation and locking delays.