NOTE
Using Spring AOP
Pointcuts, advice, proxies, aspect ordering, and the self-invocation limitation of proxy-based Spring AOP.
This is a historical learning note and may contain outdated or incomplete understanding.
Spring AOP applies cross-cutting behavior such as transactions, metrics, authorization, or logging around matched method executions, commonly through proxies.
Define pointcuts narrowly and keep advice behavior observable/predictable. Proxy-based AOP means calls that bypass the proxy—especially ordinary self-invocation from one method to another on the same instance—do not automatically pass through advice.
Do not use aspects to hide core business control flow; reserve them for genuinely cross-cutting policy.