Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

비관적 락 사용한 조회 호출에 대한 재시도 처리 적용 #297

Merged
merged 5 commits into from
Mar 19, 2024
Merged

비관적 락 사용한 조회 호출에 대한 재시도 처리 적용 #297

merged 5 commits into from
Mar 19, 2024

Commits on Mar 17, 2024

  1. refactor : BuyQueryService 에서 비관적 락 사용한 조회 호출 시, retry 매커니즘 적용 

    - @retryable 적용
- delay 100ms 설정
    @vanillacake369
    vanillacake369 committed Mar 17, 2024
    Configuration menu
    Copy the full SHA
    0c85a1a View commit details
    Browse the repository at this point in the history

  2. refactor : SellQueryService 에서 비관적 락 사용한 조회 호출 시, retry 매커니즘 적용 

    - @retryable 적용
- delay 100ms 설정
    @vanillacake369
    vanillacake369 committed Mar 17, 2024
    Configuration menu
    Copy the full SHA
    2c47aa2 View commit details
    Browse the repository at this point in the history

  3. feat : BuyQueryService 에서 비관적 락 사용한 조회 호출 시, retry 매커니즘 적용 

    - @retryable 적용
- delay 100ms 설정
    @vanillacake369
    vanillacake369 committed Mar 17, 2024
    Configuration menu
    Copy the full SHA
    d802fcd View commit details
    Browse the repository at this point in the history

  4. feat : SellQueryService 에서 비관적 락 사용한 조회 호출 시, retry 매커니즘 적용 

    - @retryable 적용
- delay 100ms 설정
    @vanillacake369
    vanillacake369 committed Mar 17, 2024
    Configuration menu
    Copy the full SHA
    d989ac3 View commit details
    Browse the repository at this point in the history

  5. Merge remote-tracking branch 'origin/refactor/add-retry-on-pessimisti… 

    …c-lock' into improvement/add-retry-on-pessimistic-lock
    @vanillacake369
    vanillacake369 committed Mar 17, 2024
    Configuration menu
    Copy the full SHA
    82327ff View commit details
    Browse the repository at this point in the history