AOP for performance monitoring in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AOP in the context of Spring Boot?

AOP stands for Aspect-Oriented Programming. It helps separate cross-cutting concerns like logging or performance monitoring from business logic by using aspects.

beginner

How does AOP help in performance monitoring?

AOP allows you to add code that measures method execution time without changing the original method code. This keeps the code clean and focused.

intermediate

What is an advice in AOP?

Advice is the action taken by an aspect at a particular join point, like before or after a method runs. For performance, you often use 'around' advice to measure time.

beginner

Which annotation is used to define an aspect in Spring Boot?

The @Aspect annotation marks a class as an aspect that contains advice and pointcuts.

intermediate

What is a pointcut in AOP?

A pointcut defines where an advice should be applied, like which methods or classes to target for performance monitoring.

Which AOP advice type is best for measuring method execution time?

A After returning advice

B Around advice

C Before advice

D After throwing advice

Around advice wraps the method execution, allowing you to measure time before and after the method runs.

What annotation marks a class as an aspect in Spring Boot?

A @Aspect

B @Component

C @Service

D @Controller

The @Aspect annotation identifies a class as an aspect containing advice and pointcuts.

What does a pointcut specify in AOP?

A The method return type

B The code to execute

C Where advice should apply

D The exception to handle

A pointcut defines the join points (like methods) where advice should be applied.

Why use AOP for performance monitoring?

A To separate monitoring code from business code

B To rewrite business logic

C To slow down the application

D To handle exceptions

AOP keeps performance monitoring code separate, making the main code cleaner and easier to maintain.

Which Spring Boot dependency is needed for AOP?

A spring-boot-starter-web

B spring-boot-starter-security

C spring-boot-starter-data-jpa

D spring-boot-starter-aop

The spring-boot-starter-aop dependency enables AOP support in Spring Boot.

Explain how you would use AOP in Spring Boot to measure the execution time of service methods.

Think about wrapping the method call to measure time before and after.

What are the benefits of using AOP for performance monitoring compared to adding timing code directly inside methods?

Consider code cleanliness and maintenance.

Practice

1. What is the main purpose of using AOP for performance monitoring in Spring Boot?

easy

A. To measure method execution time without changing the method code

B. To change the business logic of methods

C. To add new REST endpoints automatically

D. To replace database queries with cached results

Solution

1. Step 1: Understand AOP's role in performance monitoring

   AOP allows adding extra code around methods without modifying their original code.

2. Step 2: Identify the purpose of timing code

   Timing code measures how long methods take to run, helping find slow parts.

3. Final Answer:

   To measure method execution time without changing the method code -> Option A

4. Quick Check:

   AOP measures time without code changes [OK]

Hint: AOP adds timing code outside main methods [OK]

Common Mistakes:

• Thinking AOP changes method logic
• Confusing AOP with adding endpoints
• Assuming AOP caches database queries

2. Which annotation is used in Spring AOP to wrap method execution for timing?

easy

A. @Before

B. @After

C. @Around

D. @Pointcut

Solution

1. Step 1: Recall Spring AOP advice types

   @Before runs before method, @After runs after, @Around wraps method execution.

2. Step 2: Identify which advice can measure execution time

   @Around can run code before and after method, so it can measure duration.

3. Final Answer:

   @Around -> Option C

4. Quick Check:

   @Around wraps method for timing [OK]

Hint: Use @Around to wrap and time methods [OK]

Common Mistakes:

• Using @Before or @After which can't measure duration
• Confusing @Pointcut with advice annotation
• Assuming @After runs before method

3. Given this AOP method, what will be printed if the target method takes 150ms to execute?

@Around("execution(* com.example.service.*.*(..))")
public Object measureTime(ProceedingJoinPoint pjp) throws Throwable {
  long start = System.currentTimeMillis();
  Object result = pjp.proceed();
  long end = System.currentTimeMillis();
  System.out.println("Execution time: " + (end - start) + " ms");
  return result;
}

medium

A. Execution time: 0 ms

B. No output printed

C. Execution time: 300 ms

D. Execution time: 150 ms

Solution

1. Step 1: Understand timing calculation

   The code records start time, runs the method, then records end time and prints the difference.

2. Step 2: Match timing with method duration

   If method takes 150ms, printed time is 150 ms.

3. Final Answer:

   Execution time: 150 ms -> Option D

4. Quick Check:

   Printed time matches method duration [OK]

Hint: Printed time equals method run duration [OK]

Common Mistakes:

• Assuming time is zero or double counted
• Thinking no output prints
• Confusing start and end time order

4. What is wrong with this AOP advice for measuring execution time?

@Around("execution(* com.example..*(..))")
public void measure(ProceedingJoinPoint pjp) throws Throwable {
  long start = System.currentTimeMillis();
  pjp.proceed();
  long end = System.currentTimeMillis();
  System.out.println("Time: " + (end - start));
}

medium

A. The pointcut expression is invalid

B. The method should return Object, not void

C. System.currentTimeMillis() cannot be used for timing

D. ProceedingJoinPoint cannot be used in @Around advice

Solution

1. Step 1: Check method signature for @Around advice

   @Around advice must return the result of pjp.proceed() to maintain method behavior.

2. Step 2: Identify missing return statement

   Method returns void but should return Object from pjp.proceed().

3. Final Answer:

   The method should return Object, not void -> Option B

4. Quick Check:

   @Around advice must return method result [OK]

Hint: @Around methods must return Object from proceed() [OK]

Common Mistakes:

• Forgetting to return pjp.proceed() result
• Thinking pointcut syntax is wrong
• Believing System.currentTimeMillis() is invalid

5. You want to monitor execution time of all service methods but exclude methods annotated with @SkipTiming. Which AOP pointcut expression correctly achieves this?

hard

A. execution(* com.example.service..*(..)) && !@annotation(com.example.SkipTiming)

B. execution(* com.example.service..*(..)) || @annotation(com.example.SkipTiming)

C. execution(* com.example.service..*(..)) && @annotation(com.example.SkipTiming)

D. !execution(* com.example.service..*(..)) && !@annotation(com.example.SkipTiming)

Solution

1. Step 1: Understand pointcut logic for inclusion and exclusion

   We want all service methods except those with @SkipTiming annotation.

2. Step 2: Use && with negation to exclude annotated methods

   Use 'execution(...) && !@annotation(...)' to include methods but exclude those annotated.

3. Final Answer:

   execution(* com.example.service..*(..)) && !@annotation(com.example.SkipTiming) -> Option A

4. Quick Check:

   Exclude annotated methods with !@annotation [OK]

Hint: Use && !@annotation to exclude methods [OK]

Common Mistakes:

• Using || which includes annotated methods
• Using && @annotation which includes only annotated
• Negating execution pointcut incorrectly