Ignore: 🔧 30x Performance Improvement in PreAuthorize AOP #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
작업 이유
@PreAuthorize
annotation to verify user authentication in the socket module.StandardEvaluationContext
in a concurrent environment.Spring AOP
, as it felt cumbersome and inefficient.작업 사항
1️⃣ Before
@PreAuthorize
annotation relies on string-based expressions.StandardEvaluationContext
, but since Spring beans are highly dynamic, this negatively impacts caching performance.2️⃣ After
PreAuthorizer
provides four methods:methodName
could be improved, the overall design ensures better type safety.3️⃣ Benchmark
Looking at the warm-up performance data:
리뷰어가 중점적으로 확인해야 하는 부분
발견한 이슈
Long
types in Kotlin manager classes, Kotlin automatically converts them to the optimal primitive type (long
).java.lang.Long
, causing type mismatch errors.