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

Namespace Redis Connections #189

Closed
2 of 4 tasks
wilwade opened this issue May 2, 2024 · 0 comments · Fixed by #349
Closed
2 of 4 tasks

Namespace Redis Connections #189

wilwade opened this issue May 2, 2024 · 0 comments · Fixed by #349
Assignees
Labels
bug Something isn't working

Comments

@wilwade
Copy link
Contributor

wilwade commented May 2, 2024

We want to allow for all services to use the same Redis.

  • Make sure each service has a different Redis connection namespace for non-bull redis connections.
  • Make sure all Bull Queues have unique names via prefixing the queues
  • Note this as a BREAKING change

Services:

  • Graph Service
  • Account Service
  • Content Publishing Service
  • Content Watcher Service
@wilwade wilwade added the bug Something isn't working label May 2, 2024
@mattheworris mattheworris linked a pull request Aug 7, 2024 that will close this issue
4 tasks
mattheworris added a commit that referenced this issue Aug 8, 2024
We want to allow for all services to use the same Redis.

- Make sure each service has a different Redis connection namespace for
non-bull redis connections.
- Make sure all Bull Queues have unique names via prefixing the queues
- Note this as a BREAKING change

Services:

- [x] Graph Service
- [x] Account Service
- [x] Content Publishing Service
- [x] Content Watcher Service

Closes #189
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants