You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am planning to modify the logic used for inserting and scanning the ranking entity.
why
There is currently an inefficiency in ranking feature, as multiple records are being inserted into the ranking table even when the game event occurs only once. While this can improve efficiency when searching for rankers with multiple workout types, given that reading rankers does not occur as often as insertion and allows for some delay or error, I have decided to modify the logic and improve overall system efficiency.
how
I will modify the logic by inserting only one record after the game has finished.
The feature to calculate rankings will be transferred to Rankservice.
The text was updated successfully, but these errors were encountered:
YuyeonHan
changed the title
[Rank Feat] Plans to refactor ranking feature
[Rank Feat] Refactoring Plans for Ranking Feature
May 7, 2023
what
I am planning to modify the logic used for inserting and scanning the ranking entity.
why
There is currently an inefficiency in ranking feature, as multiple records are being inserted into the ranking table even when the game event occurs only once. While this can improve efficiency when searching for rankers with multiple workout types, given that reading rankers does not occur as often as insertion and allows for some delay or error, I have decided to modify the logic and improve overall system efficiency.
how
I will modify the logic by inserting only one record after the game has finished.
The feature to calculate rankings will be transferred to Rankservice.
The text was updated successfully, but these errors were encountered: