Introducing Redis for caching - #8853
Open
NoahTheDuke wants to merge 3 commits into
Open
NoahTheDuke wants to merge 3 commits into
NoahTheDuke wants to merge 3 commits into
Conversation
NoahTheDuke
force-pushed
the
nb/redis
branch
4 times, most recently
from
September 4, 2026 13:26
325ca9d to
b5a606b
Compare
NoahTheDuke
force-pushed
the
nb/redis
branch
from
September 21, 2026 17:40
b5a606b to
5949449
Compare
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
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.
NOTE: This is built on #8844, so just read the commits starting with "Add redis to our tech stack".
We need something for in-memory caching that isn't just atoms as those have contention. To actually use this, we'll need to set up redis community on prod and i guess in docker? idk shit about docker. but in prod it should be as easy as sudo apt-get or whatever.
In this pr, redis is being used for:
There are some other good uses (lobby->user, user->lobby) but they'll take more work. I don't want this PR to get too big.