Why AOP matters in Spring Boot - Performance Evidence

Performance: Why AOP matters

MEDIUM IMPACT

AOP affects runtime performance by adding method interception layers, impacting CPU usage and response time.

Adding logging to multiple service methods

Spring Boot

@Aspect
@Component
public class LoggingAspect {
  @Before("execution(* com.example.service.*.*(..))")
  public void logStart(JoinPoint joinPoint) {
    System.out.println("Start " + joinPoint.getSignature().getName());
  }
  @After("execution(* com.example.service.*.*(..))")
  public void logEnd(JoinPoint joinPoint) {
    System.out.println("End " + joinPoint.getSignature().getName());
  }
}

Centralizes logging logic, reducing code duplication and improving maintainability.

📈 Performance GainSaves CPU cycles by avoiding redundant code and reduces codebase size.

Adding logging to multiple service methods

Spring Boot

public class UserService {
  public void createUser() {
    System.out.println("Start createUser");
    // method logic
    System.out.println("End createUser");
  }
  public void deleteUser() {
    System.out.println("Start deleteUser");
    // method logic
    System.out.println("End deleteUser");
  }
}

Logging code is duplicated in every method, increasing code size and maintenance effort.

📉 Performance CostIncreases code size and CPU usage due to repeated logging calls.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual logging in each method	N/A	N/A	N/A	[X] Bad
Centralized logging with AOP	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

AOP weaves additional code around method calls at runtime, adding interception layers before and after method execution.

→Method Invocation

→CPU Processing

⚠️ BottleneckMethod Invocation overhead due to proxy creation and advice execution.

Core Web Vital Affected

INP

AOP affects runtime performance by adding method interception layers, impacting CPU usage and response time.

Optimization Tips

1AOP adds method call overhead but improves code modularity.

2Limit advice to necessary methods to reduce CPU cost.

3Use profiling tools to measure AOP impact on response time.

Performance Quiz - 3 Questions

What is the main performance cost of using AOP in Spring Boot?

A Increased network latency

B Additional method call overhead due to proxies

C More database queries

D Larger HTML payloads

DevTools: Spring Boot Actuator and Java Profilers

How to check: Use a Java profiler to measure method execution time and CPU usage with and without AOP advice.

What to look for: Look for increased method call duration and CPU overhead caused by AOP proxies.

Practice

1. What is the main purpose of Aspect-Oriented Programming (AOP) in Spring Boot?

easy

A. To separate common tasks like logging and security from business logic

B. To replace the need for writing any business logic

C. To make the application run faster by skipping method calls

D. To store data in the database automatically

Solution

1. Step 1: Understand AOP's role

   AOP helps keep common tasks like logging or security separate from the main business code.

2. Step 2: Identify the main benefit

   This separation makes the code easier to read and maintain without changing the business logic itself.

3. Final Answer:

   To separate common tasks like logging and security from business logic -> Option A

4. Quick Check:

   AOP separates concerns = D [OK]

Hint: AOP separates cross-cutting tasks from main code [OK]

Common Mistakes:

• Thinking AOP replaces business logic
• Believing AOP speeds up method execution
• Confusing AOP with database operations

2. Which of the following is the correct way to define an aspect in Spring Boot using AOP?

easy

A. @Component
public class MyAspect { }

B. @Aspect
public class MyAspect { }

C. @Service
public class MyAspect { }

D. @Repository
public class MyAspect { }

Solution

1. Step 1: Recognize the annotation for aspects

   In Spring AOP, the @Aspect annotation marks a class as an aspect.

2. Step 2: Confirm the correct syntax

   Only @Aspect correctly defines an aspect; @Component alone does not define aspect behavior.

3. Final Answer:

   @Aspect public class MyAspect { } -> Option B

4. Quick Check:

   @Aspect marks aspect classes = B [OK]

Hint: Use @Aspect to define aspects in Spring Boot [OK]

Common Mistakes:

• Using @Component alone without @Aspect
• Confusing @Service or @Repository with aspects
• Missing the @Aspect annotation

3. Given this Spring Boot aspect code snippet, what will be printed when myService.doWork() is called?

@Aspect
@Component
public class LoggingAspect {
  @Before("execution(* com.example.MyService.doWork(..))")
  public void logBefore() {
    System.out.println("Starting work");
  }
}

@Service
public class MyService {
  public void doWork() {
    System.out.println("Doing work");
  }
}

medium

A. Starting work
Doing work

B. Doing work
Starting work

C. Doing work

D. Starting work

Solution

1. Step 1: Understand @Before advice

   The @Before advice runs before the target method, so "Starting work" prints first.

2. Step 2: Trace method call output

   Then the actual method prints "Doing work" after the advice.

3. Final Answer:

   Starting work Doing work -> Option A

4. Quick Check:

   @Before runs before method = A [OK]

Hint: @Before advice runs before method call output [OK]

Common Mistakes:

• Assuming advice runs after method
• Mixing order of printed lines
• Ignoring advice output

4. Identify the error in this Spring Boot aspect code that prevents the advice from running:

@Aspect
@Component
public class SecurityAspect {
  @Before("execution(* com.example.MyService.secureMethod())")
  public void checkSecurity() {
    System.out.println("Checking security");
  }
}

@Service
public class MyService {
  public void secureMethod(String user) {
    System.out.println("Secure method for " + user);
  }
}

medium

A. secureMethod should be private

B. Missing @Component annotation on MyService

C. Advice method must return a value

D. The pointcut expression does not match the method signature

Solution

1. Step 1: Compare pointcut and method signature

   The pointcut expects a method with no parameters, but secureMethod takes a String parameter.

2. Step 2: Understand pointcut matching rules

   Because the signature does not match, the advice never runs.

3. Final Answer:

   The pointcut expression does not match the method signature -> Option D

4. Quick Check:

   Pointcut must match method signature = A [OK]

Hint: Match pointcut exactly to method signature [OK]

Common Mistakes:

• Ignoring method parameters in pointcut
• Thinking @Component missing on service blocks advice
• Believing advice must return a value

5. You want to add logging before and after all methods in your service without changing each method. Which AOP approach best achieves this in Spring Boot?

hard

A. Create a new service class that duplicates all methods with logging

B. Manually add logging code inside every service method

C. Use @Before and @After advices with a pointcut matching all service methods

D. Use @Transactional annotation on service methods

Solution

1. Step 1: Identify the goal

   You want to add logging around all service methods without modifying them individually.

2. Step 2: Choose the correct AOP approach

   @Before and @After advices with a pointcut covering all service methods allow running code before and after each method automatically.

3. Final Answer:

   Use @Before and @After advices with a pointcut matching all service methods -> Option C

4. Quick Check:

   AOP advices automate cross-cutting tasks = C [OK]

Hint: Use @Before and @After with pointcut for all methods [OK]

Common Mistakes:

• Adding logging manually in every method
• Duplicating service classes unnecessarily
• Confusing logging with transaction management