Spring AOP Lab

Make cross-cutting behavior visible instead of abstract.

This page focuses on the parts students usually miss: where advice wraps controller and service methods, how timing is collected, and why a validation failure still counts as observed runtime behavior.

Recommended AOP sequence

1. Trigger controller calls

Run the list and stats endpoints to make sure both controller and service methods execute.

2. Trigger a validation failure

Send an invalid user payload and compare the failed request with the successful ones.

3. Inspect aspect output

Load the stats endpoint and compare call counts, total time, and average time.

Advice Map

@Before @After @AfterReturning @AfterThrowing @Around

Before

Inspect inputs or auth context.

Around

Start timer and continue the join point.

Controller

Delegate work to the service.

Service

Apply business logic.

After*

Record result or failure details.

Live Runs

Run requests and inspect collected metrics

The buttons below help you create real traffic, then inspect the aspect output without switching tools.

What to observe in the console

Look for controller and service timing lines. Compare success and failure paths to see how around advice still records method duration.

What to inspect in code

Read PerformanceAspect first, then compare it with the user endpoints that it wraps.

Run one of the experiments above to inspect live JSON output.