[GH-ISSUE #88] Introduce pool member caching to backend #65

New issue

Closed

opened 2026-02-27 19:16:43 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 19:16:43 +03:00

Owner

Originally created by @EddieTheCubeHead on GitHub (Feb 23, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/88

Whenever a pool member data is required, the app should first check in internal database ("cache") for existing data. Data should be fetched from spotify only if it doesn't exist. Fetched data should be then saved to internal database.

Acceptance criteria: core only fetches pool member data for pool members that have never been fetched before. Functionality is fully tested, including edge cases.

Originally created by @EddieTheCubeHead on GitHub (Feb 23, 2024). Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/88 Whenever a pool member data is required, the app should first check in internal database ("cache") for existing data. Data should be fetched from spotify only if it doesn't exist. Fetched data should be then saved to internal database. Acceptance criteria: core only fetches pool member data for pool members that have never been fetched before. Functionality is fully tested, including edge cases.