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

Separate Redis Access for Core and Sub Operations #3536

Open
HyeockJinKim opened this issue Jan 23, 2025 — with Lablup-Issue-Syncer · 0 comments
Open

Separate Redis Access for Core and Sub Operations #3536

HyeockJinKim opened this issue Jan 23, 2025 — with Lablup-Issue-Syncer · 0 comments
Assignees

Comments

@HyeockJinKim
Copy link
Collaborator

Motivation  

  • To ensure that less critical Redis operations do not impact core operations.

Objective  

  • Apply code to route requests to different Redis instances based on priority

�Expected Sub Issue

  • Categorize Redis client usage by priority. (Task)
  • Inject different Redis clients based on the importance of Redis usage.
@HyeockJinKim HyeockJinKim self-assigned this Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant