CRUD methods (save, findById, findAll, delete) in Spring Boot - Performance & Optimization

Performance: CRUD methods (save, findById, findAll, delete)

MEDIUM IMPACT

This concept affects how quickly data operations respond and how much the UI waits for data changes, impacting user interaction speed and perceived responsiveness.

Fetching all records from a database

Spring Boot

Page<Entity> findAll(Pageable pageable) { return repository.findAll(pageable); } // fetches data in pages

Fetching data in pages reduces memory use and speeds up response time.

📈 Performance GainReduces blocking time to tens of milliseconds per page

Fetching all records from a database

Spring Boot

List<Entity> findAll() { return repository.findAll(); } // fetches all data without pagination

Fetching all records at once can overload memory and delay response, especially with large datasets.

📉 Performance CostBlocks response for hundreds of milliseconds or more depending on data size

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Fetch all without pagination	N/A	N/A	Blocks UI update waiting for data	[X] Bad
Fetch with pagination	N/A	N/A	Allows incremental UI updates	[OK] Good
Save without check	N/A	N/A	Causes unnecessary DB writes delaying response	[X] Bad
Save with existence check	N/A	N/A	Reduces DB writes improving response	[OK] Good
Delete without check	N/A	N/A	May cause errors and wasted DB calls	[X] Bad
Delete with existence check	N/A	N/A	Avoids errors and unnecessary DB load	[OK] Good

Rendering Pipeline

CRUD methods impact the server response time which affects when the browser can paint updated content. Slow CRUD calls delay the browser's ability to update the UI.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing due to database query and write latency

Core Web Vital Affected

INP

This concept affects how quickly data operations respond and how much the UI waits for data changes, impacting user interaction speed and perceived responsiveness.

Optimization Tips

1Use pagination to limit data fetched in findAll methods.

2Check if an entity exists before saving or deleting to avoid unnecessary database operations.

3Avoid fetching or manipulating large data sets in a single operation to keep UI responsive.

Performance Quiz - 3 Questions

Which CRUD pattern improves user interaction responsiveness in Spring Boot?

A Using pagination when fetching records

B Fetching all records at once

C Saving entities without checking if they exist

D Deleting entities without existence check

DevTools: Network

How to check: Open DevTools, go to Network tab, perform CRUD actions, and observe request duration and size.

What to look for: Look for long server response times or large payloads indicating slow or heavy CRUD operations.