Adding the ability to change caching strategy#62
Open
debugger84 wants to merge 1 commit intovektah:masterfrom
Open
Adding the ability to change caching strategy#62debugger84 wants to merge 1 commit intovektah:masterfrom
debugger84 wants to merge 1 commit intovektah:masterfrom
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.
It is an attempt to solve the issue #52.
These changes allow developers to disable caching, if necessary, or change the caching strategy to their own realization. For example, everybody can change storing data in the map to storing in BigCache, which has an option to set a limit of memory consumption. In our case, it helps us to avoid storing the whole database in memory.
Also, these changes are fully backward compatible.