Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis backend based on fred.rs crate #69

Open
singulared opened this issue Jul 5, 2023 · 0 comments · May be fixed by #80
Open

Redis backend based on fred.rs crate #69

singulared opened this issue Jul 5, 2023 · 0 comments · May be fixed by #80
Assignees
Labels
backend Cache backend related issues redis Redis related issues
Milestone

Comments

@singulared
Copy link
Member

Let us use https://github.com/aembke/fred.rs/ for Redis interaction instead of redis.rs.
It has multiple major features:

  • Supports clustered, centralized, and sentinel Redis deployments.
  • Optional built-in reconnection logic with multiple backoff policies.
  • Supports transactions.
  • Supports Lua scripts.
  • Automatically retry requests under bad network conditions.
  • Optional built-in tracking for network latency and payload size metrics.
  • An optional client pooling interface to round-robin requests among a pool of clients.
  • An optional sentinel client for interacting directly with sentinel nodes to manually failover servers, etc.
@singulared singulared added backend Cache backend related issues redis Redis related issues labels Jul 5, 2023
This was referenced Jul 5, 2023
@topenkoff topenkoff self-assigned this Jul 5, 2023
@singulared singulared added this to the hitboxd-alpha milestone Jul 9, 2023
@topenkoff topenkoff linked a pull request Jul 9, 2023 that will close this issue
@topenkoff topenkoff linked a pull request Jul 9, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Cache backend related issues redis Redis related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants