Redis architecture #9
Merged
Conversation
This file contains 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
Closed
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.
This is a big re-write to move to an architecture based on Redis (instead of implementing our own actor/messaging system, which could become a big headache down the road). We'll benefit from Redis' speed and support.
We probably would have needed Redis anyways for pubsub stuff, so might as well start now.
This PR doesn't have this implemented yet, but it should be easy to switch to a Redis Cluster as well (there's no good rust library for it yet).
These changes also make the APIs for the end-user a lot simpler and cleaner. There's still more testing/experimentation needed to check if it's flexible enough, but so far it seems good.