-
Notifications
You must be signed in to change notification settings - Fork 1
Research replacing in-memory sessions with persistent storage #37
Copy link
Copy link
Open
Labels
backendBackend and API workBackend and API workdataData model, storage, or persistence workData model, storage, or persistence workdocumentationDocumentation improvementsDocumentation improvementshighComplex issue, suggested 200-point complexityComplex issue, suggested 200-point complexityresearchResearch and architecture planningResearch and architecture planningwave-readyReady for Drips Wave submissionReady for Drips Wave submission
Description
Metadata
Metadata
Assignees
Labels
backendBackend and API workBackend and API workdataData model, storage, or persistence workData model, storage, or persistence workdocumentationDocumentation improvementsDocumentation improvementshighComplex issue, suggested 200-point complexityComplex issue, suggested 200-point complexityresearchResearch and architecture planningResearch and architecture planningwave-readyReady for Drips Wave submissionReady for Drips Wave submission
Type
Fields
Give feedbackNo fields configured for issues without a type.
Research replacing in-memory sessions with persistent storage
Repository:
PolymorphicAI/study-copilotSuggested Labels: documentation, backend, data, research, high, wave-ready
Suggested Complexity: High / 200 points
Summary
Research options for replacing in-memory session/progress data with persistent storage.
Why This Matters
Persistent storage would support real user history, bookmarks, and sessions.
Tasks
Acceptance Criteria
Suggested Complexity
High / 200 points
Suggested Labels
documentation, backend, data, research, high, wave-ready