CIRCSTORE-642 Implement cache for locations and service-points API calls#552
Open
roman-barannyk wants to merge 5 commits intomasterfrom
Open
CIRCSTORE-642 Implement cache for locations and service-points API calls#552roman-barannyk wants to merge 5 commits intomasterfrom
roman-barannyk wants to merge 5 commits intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose
We are seeing elevated calls to mod-inventory-storage from mod-circulation-storage during bulk operations. It is causing instability at mod-inventory-storage which requires more resources to stay alive during acceptable customer actions. This increases hosting costs and reduced customer experience when certain calls fails and have to be re-executed within the bulk operation.
The endpoints exercised are /locations and /service-points. Within a minute duration, we are seeing 52K calls each to retrieve location and service-point data. For example, Kafka item-update events trigger up to 2 sequential HTTP calls to /locations and /service-points with zero caching. This results in massive redundant traffic during bulk item updates
Resolves: CIRCSTORE-642