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

Song history should be managed in the database, not in memory #245

Open
kenellorando opened this issue Mar 26, 2023 · 0 comments
Open

Song history should be managed in the database, not in memory #245

kenellorando opened this issue Mar 26, 2023 · 0 comments
Assignees
Labels
domain: cadence-api Relates to cadence API

Comments

@kenellorando
Copy link
Owner

Since song history data is in-memory, it does not fully function properly when Cadence scales beyond one replica. Each replica maintains its own copy of song history.

If we moved this data into one of the databases, we would be properly separate API and data, and only keep one master copy of it instead of having each replica duplicate it.

Depends on #224.

@kenellorando kenellorando added the domain: cadence-api Relates to cadence API label Mar 26, 2023
@kenellorando kenellorando self-assigned this Mar 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: cadence-api Relates to cadence API
Projects
None yet
Development

No branches or pull requests

1 participant