Migrate from Memcache to Solid Cache (postgresql) - #6305
Draft
colby-swandale wants to merge 1 commit into
Draft
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.
Migrate Rails.cache from Memcached to Solid Cache, which stores cache entries in PostgreSQL. This eliminates memcached as an external service dependency, simplifying both local development setup and production infrastructure.
This PR will require some coordination to ensure that we're able to smoothly migrate from Memcache to Solid Cache without affecting production. User session data is signed and encrypted in Cookies, but we use Rails cache for Rate Limiting & Compact Index data.
We don't yet have a database setup for Solid Cache, but will circle back with the new details in the near future.