refactor service caching #855
Open
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
hedibouattour
force-pushed
the
refactor-service-caching
branch
from
33935b7 to
f8d2794
Compare
hedibouattour
force-pushed
the
refactor-service-caching
branch
from
f8d2794 to
ea85208
Compare
Previously, entries were cached by entry key only. This caused issues when multiple services referenced the same entry. This update changes the caching logic to: * Cache each entry by service ID while allowing multiple services to target the same entry. * When multiple services reference the same entry, override the previous value and keep the latest. * On service entry deletion, check whether other services still reference the same entry; if so, recreate the entry. This ensures consistent behavior when entries are shared across services.
hedibouattour
force-pushed
the
refactor-service-caching
branch
from
ea85208 to
35634e5
Compare
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.
Previously, entries were cached by entry key only. This caused issues when multiple services referenced the same entry.
This update changes the caching logic to:
Cache each entry by service ID while allowing multiple services to target the same entry.
When multiple services reference the same entry, override the previous value and keep the latest.
On service entry deletion, check whether other services still reference the same entry; if so, recreate the entry.
This ensures consistent behavior when entries are shared across services.