feat: api cache system with dragonfly #436
Merged
Conversation
This file contains 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
github-actions
bot
added
the
state/triage 🚦
Terraform data for
|
Terraform data for
|
Terraform data for
|
Terraform data for
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe the pull request
This Pull Request introduces a new feature to our API - a cache system implemented with Dragonfly. The cache system is primarily used to cache all proxies from the intranet, aiming to prevent bursts on the intra API. By caching frequently requested data, the system reduces the load on the intra API, resulting in improved performance and response time.
Dragonfly, a robust caching library, is utilized to handle the caching mechanism effectively, providing features such as cache expiration and invalidation. The cache system is designed to gracefully handle cache expiration and ensure that the most up-to-date data is served to the users.
Checklist
Breaking changes ?
no