Business logic in services in Spring Boot

Introduction

Business logic in services means putting the main rules and decisions of your app in special parts called services. This keeps your code clean and easy to change.

When you want to keep your controller code simple and focused on handling web requests.

When you need to reuse the same business rules in different parts of your app.

When you want to separate how data is stored from how your app works.

When you want to test your app's main logic without dealing with web or database details.

When your app grows and you want to keep it organized and easy to maintain.

Syntax

Spring Boot

public class SomeService {
    // Business logic methods
    public ReturnType methodName(Parameters) {
        // rules and decisions here
    }
}

Services are usually marked with @Service annotation in Spring Boot.

Services are called by controllers or other parts of the app to perform tasks.

Examples

This service calculates the total price of an order by adding up item prices times quantities.

Spring Boot

@Service
public class OrderService {
    public double calculateTotalPrice(Order order) {
        double total = 0;
        for (Item item : order.getItems()) {
            total += item.getPrice() * item.getQuantity();
        }
        return total;
    }
}

This service checks if a user is active and has the admin role to allow access.

Spring Boot

@Service
public class UserService {
    public boolean canUserAccessFeature(User user) {
        return user.isActive() && user.getRole().equals("ADMIN");
    }
}

Sample Program

This example shows a CalculatorService with business logic for adding and multiplying numbers. The CalculatorController calls this service to handle web requests. This keeps the logic separate from the web code.

Spring Boot

package com.example.demo.service;

import org.springframework.stereotype.Service;

@Service
public class CalculatorService {
    public int add(int a, int b) {
        return a + b;
    }

    public int multiply(int a, int b) {
        return a * b;
    }
}

package com.example.demo.controller;

import com.example.demo.service.CalculatorService;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestParam;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class CalculatorController {

    private final CalculatorService calculatorService;

    public CalculatorController(CalculatorService calculatorService) {
        this.calculatorService = calculatorService;
    }

    @GetMapping("/add")
    public int add(@RequestParam int a, @RequestParam int b) {
        return calculatorService.add(a, b);
    }

    @GetMapping("/multiply")
    public int multiply(@RequestParam int a, @RequestParam int b) {
        return calculatorService.multiply(a, b);
    }
}

Important Notes

Keep business logic in services to make your app easier to test and maintain.

Controllers should only handle web requests and responses, not complex logic.

Use dependency injection to get service instances in controllers.

Summary

Business logic belongs in services, not controllers or repositories.

Services help keep code organized and reusable.

Spring Boot uses @Service to mark service classes.

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