Business logic in services in Spring Boot - Performance & Optimization

Performance: Business logic in services

MEDIUM IMPACT

This affects server response time and how quickly the backend can process requests, impacting the overall user experience and perceived page speed.

Implementing business logic for user data processing

Spring Boot

public User processUserData(User user) {
    validateUser(user); // Separate validation
    User savedUser = userRepository.save(user); // DB call isolated
    int score = calculateScore(savedUser); // Pure logic separated
    savedUser.setScore(score);
    return savedUser;
}

private void validateUser(User user) {
    if (user.getName() == null) {
        throw new IllegalArgumentException("Name required");
    }
}

Separating concerns reduces complexity and allows faster processing and easier optimization.

📈 Performance GainReduces blocking time by 30-50ms and improves maintainability

Implementing business logic for user data processing

Spring Boot

public User processUserData(User user) {
    // Business logic mixed with database calls and validation
    if (user.getName() == null) {
        throw new IllegalArgumentException("Name required");
    }
    user.setScore(calculateScore(user));
    userRepository.save(user); // Direct DB call inside logic
    return user;
}

Mixing database calls and complex logic in one method causes slower response and harder maintenance.

📉 Performance CostBlocks request processing longer, increasing server response time by 50-100ms per call

Performance Comparison

Pattern	Server Processing Time	Database Calls	Code Complexity	Verdict
Mixed logic with DB calls inline	High (slow)	Multiple per request	High	[X] Bad
Separated validation, DB, and logic	Low (faster)	Minimal per request	Low	[OK] Good

Rendering Pipeline

Business logic in services runs on the server before the response reaches the browser. Efficient logic reduces server processing time, leading to faster data delivery and improved interaction responsiveness.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (business logic execution)

Core Web Vital Affected

INP

This affects server response time and how quickly the backend can process requests, impacting the overall user experience and perceived page speed.

Optimization Tips

1Keep business logic modular and separate from database calls.

2Avoid complex calculations inline with data access to reduce blocking time.

3Use caching and asynchronous processing where possible to speed up responses.

Performance Quiz - 3 Questions

How does mixing database calls directly inside business logic methods affect performance?

A It increases server response time by blocking processing longer

B It reduces server response time by combining operations

C It has no effect on performance

D It improves browser rendering speed

DevTools: Network and Performance panels

How to check: Use Network panel to measure backend response time; use Performance panel to record and analyze server response delays.

What to look for: Look for long server response times (TTFB) indicating slow business logic processing.

Practice

1. In Spring Boot, where should the main business logic of an application be placed?

easy

A. Inside a class annotated with @Service

B. Directly inside the controller methods

C. Within the repository interfaces

D. In the main application class

Solution

1. Step 1: Understand Spring Boot layering

   Controllers handle HTTP requests, repositories handle data access, and services contain business logic.

2. Step 2: Identify the correct annotation for business logic

   The @Service annotation marks classes that hold business logic in Spring Boot.

3. Final Answer:

   Inside a class annotated with @Service -> Option A

4. Quick Check:

   Business logic = @Service class [OK]

Hint: Business logic goes in @Service classes, not controllers or repos [OK]

Common Mistakes:

• Putting business logic in controllers
• Adding logic inside repository interfaces
• Mixing business logic in the main application class

2. Which of the following is the correct way to declare a service class in Spring Boot?

easy

A. @Service public class UserService {}

B. public class UserService {}

C. @Repository public class UserService {}

D. @Controller public class UserService {}

Solution

1. Step 1: Recognize the annotation for service classes

   Spring Boot uses @Service to mark service classes that contain business logic.

2. Step 2: Check the options for correct annotation

   Only @Service public class UserService {} uses @Service correctly on the class declaration.

3. Final Answer:

   @Service public class UserService {} -> Option A

4. Quick Check:

   Service class = @Service annotation [OK]

Hint: Use @Service annotation to mark service classes [OK]

Common Mistakes:

• Using @Repository or @Controller instead of @Service
• Forgetting to add any annotation
• Placing @Service on interfaces instead of classes

3. Given the following service method, what will be the output when calculateDiscount(150) is called?

public class DiscountService {
    public int calculateDiscount(int price) {
        if (price > 100) {
            return price * 20 / 100;
        } else {
            return price * 10 / 100;
        }
    }
}

medium

A. 20

B. 30

C. 10

D. 15

Solution

1. Step 1: Check the input value and condition

   The input price is 150, which is greater than 100, so the first branch applies.

2. Step 2: Calculate the discount

   Discount = 150 * 20 / 100 = 30, but since integer division is used, it remains 30.

3. Final Answer:

   30 -> Option B

4. Quick Check:

   Price > 100 -> 20% discount = 30 [OK]

Hint: Check conditions carefully and do integer math for discounts [OK]

Common Mistakes:

• Choosing 20 thinking it's the percentage, not the amount
• Confusing the else branch discount
• Ignoring integer division effects

4. Identify the error in this service class code snippet:

@Service
public class OrderService {
    @Autowired
    private OrderRepository orderRepository;

    public void saveOrder(Order order) {
        orderRepository.save(order)
    }
}

medium

A. Service class must extend a base class

B. OrderRepository should not be autowired

C. Missing semicolon after orderRepository.save(order)

D. Method saveOrder should return a value

Solution

1. Step 1: Review the method syntax

   The line orderRepository.save(order) is missing a semicolon at the end.

2. Step 2: Validate other parts

   Autowired is correct, service classes don't need to extend base classes, and void return is allowed.

3. Final Answer:

   Missing semicolon after orderRepository.save(order) -> Option C

4. Quick Check:

   Missing semicolon = syntax error [OK]

Hint: Check for missing semicolons in method calls [OK]

Common Mistakes:

• Thinking @Autowired is wrong here
• Assuming service classes must extend something
• Believing void methods must return a value

5. You want to add a new feature: calculate the total price after applying a discount and tax in your service. Which approach best follows Spring Boot's business logic principles?

public class PricingService {
    private final DiscountService discountService;
    private final TaxService taxService;

    public PricingService(DiscountService discountService, TaxService taxService) {
        this.discountService = discountService;
        this.taxService = taxService;
    }

    public double calculateFinalPrice(double price) {
        // Fill in logic here
    }
}

hard

A. Add calculation logic directly in the main application class

B. Calculate discount and tax inside controller, then call PricingService with final value

C. Put all calculation logic inside the repository layer

D. Implement calculateFinalPrice to call discountService and taxService methods, then combine results

Solution

1. Step 1: Understand separation of concerns

   Business logic should be inside service classes, not controllers, repositories, or main class.

2. Step 2: Use existing services inside PricingService

   Calling discountService and taxService methods inside calculateFinalPrice keeps logic modular and reusable.

3. Final Answer:

   Implement calculateFinalPrice to call discountService and taxService methods, then combine results -> Option D

4. Quick Check:

   Business logic in services, reuse other services [OK]

Hint: Keep logic in services and reuse other services for clean code [OK]

Common Mistakes:

• Putting logic in controller or repository layers
• Mixing logic in main application class
• Duplicating discount and tax logic outside services