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

Investigate redis usage in Detroit #1619

Open
ludtkemorgan opened this issue Apr 20, 2023 · 0 comments
Open

Investigate redis usage in Detroit #1619

ludtkemorgan opened this issue Apr 20, 2023 · 0 comments

Comments

@ludtkemorgan
Copy link
Collaborator

We removed all usages of redis from core, however it still exists in Detroit. It is being used by a throttling system as well as queueing services (e.g listings-notifications.ts).

One reason we removed redis was because it wasn't working as intended in heroku for core. We should investigate to make sure that the redis functionality is actually working as intended and if migrating off of it is a better option.

The outcome of this ticket should determine what to do with redis in Detroit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Backlog-Sprint
Needs triage
Development

No branches or pull requests

1 participant