Move persistent term cache to cachex #1003
Merged
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.
Refactors the DB-based configuration system to use
Cachex
overpersistent_term
. This is the first step in the saga of moving ENV vars to runtime configuration.Cachex was chosen for its in-memory ETS store, which will be slightly slower than
persistent_term
for reads, but eliminates the risk of accidentally hitting a global GC call.Baby steps.