@Component, @Service, @Repository, @Controller in Spring Boot - Performance & Optimization

Performance: @Component, @Service, @Repository, @Controller

MEDIUM IMPACT

These annotations affect application startup time and memory usage by controlling bean creation and scanning.

Defining beans for different application layers

Spring Boot

@Service
public class UserService { ... }

@Repository
public class UserRepository { ... }

@Controller
public class UserController { ... }

Using specific stereotypes helps Spring optimize scanning and apply layer-specific behaviors, reducing overhead.

📈 Performance GainReduces scanning overhead and memory usage; improves startup time

Defining beans for different application layers

Spring Boot

@Component
public class UserService { ... }

@Component
public class UserRepository { ... }

@Component
public class UserController { ... }

Using @Component everywhere causes Spring to scan and register all classes as generic beans, increasing startup time and memory usage.

📉 Performance CostIncreases startup time by scanning more classes; adds unnecessary beans to context

Performance Comparison

Pattern	Bean Scanning	Startup Time	Memory Usage	Verdict
@Component everywhere	High - scans all classes as generic beans	Slower due to extra scanning	Higher due to many beans	[X] Bad
@Service, @Repository, @Controller used	Optimized - scans with layer context	Faster startup	Lower memory footprint	[OK] Good

Rendering Pipeline

Spring scans classes with these annotations during startup to create and register beans in the application context.

→Classpath Scanning

→Bean Creation

→Dependency Injection

⚠️ BottleneckClasspath Scanning and Bean Creation can slow startup if too many generic @Component beans exist.

Optimization Tips

1Use @Service, @Repository, and @Controller to clearly define bean roles and optimize scanning.

2Avoid using @Component for all classes to reduce startup overhead.

3Enable debug logs to monitor bean scanning and startup performance.

Performance Quiz - 3 Questions

What is the main performance benefit of using @Service instead of @Component for service classes?

A Spring applies service-specific optimizations reducing startup time.

B It reduces network latency during requests.

C It decreases CSS rendering time in the browser.

D It automatically caches all service methods.

DevTools: Spring Boot Actuator / Logs

How to check: Enable debug logging for 'org.springframework.context' to see bean scanning details during startup.

What to look for: Look for the number of beans created and scanning duration to confirm optimized startup.

Practice

1. Which annotation is the most general one used to mark a Spring bean in a Spring Boot application?

easy

A. @Service

B. @Component

C. @Repository

D. @Controller

Solution

1. Step 1: Understand the purpose of each annotation

   @Component is the base annotation for any Spring-managed bean. @Service, @Repository, and @Controller are specialized stereotypes built on top of @Component.

2. Step 2: Identify the most general annotation

   Since @Component is the general-purpose annotation for any Spring bean, it is the correct answer.

3. Final Answer:

   @Component -> Option B

4. Quick Check:

   General Spring bean marker = @Component [OK]

Hint: General bean annotation is @Component, others are special cases [OK]

Common Mistakes:

• Confusing @Service as the general bean annotation
• Thinking @Repository is for all beans
• Assuming @Controller is the general annotation

2. Which annotation should you use to mark a class that handles HTTP requests in a Spring Boot application?

easy

A. @Repository

B. @Service

C. @Controller

D. @Component

Solution

1. Step 1: Recall the role of each annotation

   @Controller is specifically designed for classes that handle web requests and return views or data.

2. Step 2: Match the annotation to the web controller role

   Since the question asks about handling HTTP requests, @Controller is the correct annotation.

3. Final Answer:

   @Controller -> Option C

4. Quick Check:

   Web request handler = @Controller [OK]

Hint: Web controllers use @Controller annotation [OK]

Common Mistakes:

• Using @Service for web controllers
• Confusing @Repository with @Controller
• Using @Component instead of @Controller for HTTP handling

3. Consider the following Spring Boot class:

@Service
public class UserService {
    public String getUser() {
        return "Alice";
    }
}

What is the role of this class in the application?

medium

A. Contains business logic related to users

B. Accesses the database to retrieve user data

C. General Spring bean without specific role

D. Handles HTTP requests and responses

Solution

1. Step 1: Identify the annotation and its meaning

   The class is annotated with @Service, which is used for business logic components in Spring.

2. Step 2: Understand the method and class purpose

   The method getUser() returns a user name, indicating business logic rather than database access or HTTP handling.

3. Final Answer:

   Contains business logic related to users -> Option A

4. Quick Check:

   @Service = business logic class [OK]

Hint: @Service means business logic, not web or data access [OK]

Common Mistakes:

• Thinking @Service accesses the database directly
• Confusing @Service with @Controller
• Assuming @Service is a generic bean without role

4. What is wrong with this Spring Boot repository class?

@Repository
public class UserRepository {
    public void saveUser(String user) {
        // save logic
    }
}

Options: A) Class should be an interface extending JpaRepository B) Missing @Service annotation C) @Repository cannot be used on classes D) Method saveUser must return a value

medium

A. Class should be an interface extending JpaRepository

B. Missing @Service annotation

C. @Repository cannot be used on classes

D. Method saveUser must return a value

Solution

1. Step 1: Understand typical repository pattern in Spring Boot

   Spring Data JPA repositories are usually interfaces extending JpaRepository or CrudRepository to get built-in methods.

2. Step 2: Identify the issue with the class declaration

   The class is a concrete class, not an interface extending JpaRepository, so it misses Spring Data JPA features.

3. Final Answer:

   Class should be an interface extending JpaRepository -> Option A

4. Quick Check:

   Repositories usually extend JpaRepository interface [OK]

Hint: Repositories are interfaces extending JpaRepository, not plain classes [OK]

Common Mistakes:

• Thinking @Repository cannot be on classes
• Assuming @Service is needed for repositories
• Believing saveUser must return a value

5. You have a Spring Boot application with these classes:

@Component
public class UtilityHelper { }

@Service
public class OrderService { }

@Repository
public interface OrderRepository extends JpaRepository { }

@Controller
public class OrderController { }

Which statement correctly describes the roles and how Spring manages these beans?

hard

A. @Component manages data access; @Service handles web requests; @Repository is for business logic; @Controller is a utility bean

B. @Component handles web requests; @Service manages data access; @Repository is for utility beans; @Controller handles business logic

C. All annotations are interchangeable and have the same role in Spring

D. @Component is for utility beans; @Service handles business logic; @Repository manages data access; @Controller handles web requests

Solution

1. Step 1: Recall the purpose of each annotation

   @Component is a general-purpose bean, often used for utilities. @Service is for business logic. @Repository is for data access layers. @Controller is for handling web requests.

2. Step 2: Match each class role to its annotation

   UtilityHelper is a utility bean, so @Component fits. OrderService contains business logic, so @Service fits. OrderRepository accesses data, so @Repository fits. OrderController handles HTTP requests, so @Controller fits.

3. Final Answer:

   @Component is for utility beans; @Service handles business logic; @Repository manages data access; @Controller handles web requests -> Option D

4. Quick Check:

   Annotations match roles: Component-utility, Service-logic, Repository-data, Controller-web [OK]

Hint: Match annotation to role: Component-utility, Service-logic, Repository-data, Controller-web [OK]

Common Mistakes:

• Mixing up @Service and @Controller roles
• Thinking all annotations are interchangeable
• Confusing @Component with @Repository