@Component annotation in Spring Boot - Performance & Optimization

Performance: @Component annotation

MEDIUM IMPACT

This affects application startup time and memory usage by controlling bean creation and dependency injection.

Registering a Spring bean for dependency injection

Spring Boot

@Component
@Lazy
public class HeavyService {
    public HeavyService() {
        // expensive initialization
    }
}

Delays bean creation until first use, reducing startup time and memory usage initially.

📈 Performance GainSpeeds startup by avoiding unnecessary bean instantiation, saves memory until needed

Registering a Spring bean for dependency injection

Spring Boot

@Component
public class HeavyService {
    public HeavyService() {
        // expensive initialization
    }
}

Creates a heavy bean eagerly at startup even if not used immediately, increasing startup time and memory.

📉 Performance CostBlocks application startup for extra milliseconds, increases memory footprint

Performance Comparison

Pattern	Bean Creation	Startup Delay	Memory Usage	Verdict
Eager @Component	Creates all beans at startup	High delay if many heavy beans	High memory usage	[X] Bad
@Component with @Lazy	Creates beans on demand	Minimal startup delay	Lower memory usage initially	[OK] Good

Rendering Pipeline

Spring scans for @Component annotations during startup, creating and wiring beans before the app runs.

→Bean Creation

→Dependency Injection

→Application Startup

⚠️ BottleneckBean Creation stage can delay startup if many or heavy beans are created eagerly.

Optimization Tips

1Avoid creating heavy beans eagerly with @Component to reduce startup time.

2Use @Lazy on @Component beans to defer creation until needed.

3Monitor bean creation times to identify startup bottlenecks.

Performance Quiz - 3 Questions

What is the main performance impact of using @Component without @Lazy in Spring Boot?

A All beans are created eagerly at startup, increasing startup time and memory use.

B Beans are created only when first used, reducing startup time.

C Beans are never created, causing runtime errors.

D Beans are created in parallel, improving startup speed.

DevTools: Spring Boot Actuator / Logs

How to check: Enable debug logging for Spring context startup and monitor bean creation times.

What to look for: Look for long bean creation times or many beans created eagerly indicating startup bottlenecks.

Practice

1. What is the main purpose of the @Component annotation in Spring Boot?

easy

A. To mark a class so Spring automatically creates and manages its instance

B. To define a database entity

C. To configure application properties

D. To handle HTTP requests

Solution

1. Step 1: Understand the role of @Component

   The @Component annotation tells Spring to create an instance of the class and manage it automatically.

2. Step 2: Compare with other options

   The other options relate to other Spring features like entities, properties, or controllers, not @Component.

3. Final Answer:

   To mark a class so Spring automatically creates and manages its instance -> Option A

4. Quick Check:

   @Component = automatic management [OK]

Hint: Remember: @Component means Spring manages the class [OK]

Common Mistakes:

• Confusing @Component with @Entity
• Thinking it handles HTTP requests
• Assuming it configures properties

2. Which of the following is the correct way to declare a Spring component class?

easy

A. @Component public class MyService {}

B. @Service public void MyService() {}

C. public class MyService {}

D. @Component void MyService() {}

Solution

1. Step 1: Check annotation placement and class declaration

   The @Component annotation must be placed above a class declaration, like @Component public class MyService {}.

2. Step 2: Identify incorrect syntax

   A plain public class misses the annotation, annotating a method with @Service or @Component is invalid since components must be classes.

3. Final Answer:

   @Component public class MyService {} -> Option A

4. Quick Check:

   Annotation + class declaration = correct syntax [OK]

Hint: Always put @Component above a class, not a method [OK]

Common Mistakes:

• Annotating methods instead of classes
• Missing the annotation entirely
• Using wrong annotations for components

3. Given the code below, what will be the output when app.run() is called?

@Component
public class App {
  @Autowired
  private ServiceA serviceA;

  public void run() {
    System.out.println(serviceA.getName());
  }
}

@Component
public class ServiceA {
  public String getName() {
    return "ServiceA";
  }
}

medium

A. Runtime NullPointerException

B. null

C. ServiceA

D. Compilation error

Solution

1. Step 1: Understand component scanning and injection

   Both App and ServiceA are annotated with @Component, so Spring creates and manages their instances. The @Autowired injects ServiceA into App.

2. Step 2: Trace the method call

   Calling app.run() prints the result of serviceA.getName(), which returns "ServiceA".

3. Final Answer:

   ServiceA -> Option C

4. Quick Check:

   Autowired injects component = output string [OK]

Hint: If both classes are @Component, autowired works and prints value [OK]

Common Mistakes:

• Assuming serviceA is null without injection
• Confusing compilation vs runtime errors
• Forgetting to annotate both classes

4. What is the problem with the following code snippet?

@Component
public class MyComponent {
  @Autowired
  private ServiceB serviceB;

  public void doWork() {
    serviceB.perform();
  }
}

Assuming ServiceB is not annotated with @Component or any stereotype, what will happen?

medium

A. Compilation error due to missing import

B. The code will compile and run fine

C. ServiceB will be automatically created by Spring

D. Spring will throw a runtime error due to missing bean

Solution

1. Step 1: Check bean creation requirements

   Spring only manages classes annotated with @Component or similar. Since ServiceB lacks this, Spring won't create its bean.

2. Step 2: Understand autowiring consequences

   When Spring tries to inject serviceB, it finds no bean and throws a runtime error (NoSuchBeanDefinitionException).

3. Final Answer:

   Spring will throw a runtime error due to missing bean -> Option D

4. Quick Check:

   Missing @Component = runtime injection error [OK]

Hint: All injected classes must be annotated for Spring to manage [OK]

Common Mistakes:

• Assuming Spring creates beans without annotation
• Confusing compile errors with runtime errors
• Forgetting to annotate dependencies

5. You want to create two different implementations of an interface PaymentService and have Spring inject the correct one based on a custom qualifier. How should you use @Component to achieve this?

hard

A. Annotate only one implementation with @Component and inject by interface type

B. Annotate both implementations with @Component and use @Qualifier to specify which to inject

C. Use @Component only on the interface, not implementations

D. Create instances manually without @Component

Solution

1. Step 1: Annotate both implementations

   Both classes implementing PaymentService must be annotated with @Component so Spring manages them.

2. Step 2: Use @Qualifier to distinguish

   When injecting, use @Qualifier with the component name to tell Spring which implementation to use.

3. Final Answer:

   Annotate both implementations with @Component and use @Qualifier to specify which to inject -> Option B

4. Quick Check:

   Multiple components + qualifier = correct injection [OK]

Hint: Use @Component on all, @Qualifier to pick one [OK]

Common Mistakes:

• Annotating only one implementation
• Annotating interface instead of classes
• Not using @Qualifier when multiple beans exist