Why can @Async, @Transactional, and @Cacheable all silently fail on self-invocation?
PICTURE THIS: ASYNC / PROMISE
Simple meaning
They are proxy-based AOP.
WHY — Spring Boot instead of guessing?
Why interviewers care about Spring Boot:
on Spring Boot.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Define it
They are proxy-based AOP.
- 2Internal this.foo() never hits
the proxy, so you get no new thread, no transaction, and no cache.
- 3Put the annotated methods
on another bean or inject self through the context.
- 4Interviewers use this to
see if you understand Spring beyond annotations.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
They are proxy-based AOP. Internal this.foo() never hits the proxy, so you get no new thread, no transaction, and no cache.