Server Restart or Scale
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.6k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
From the looks of it, if the current server does not have the session it is looking for, then the callback will fail. The store for these sessions seems to live solely on the server. Could we get some sort of other storage implemented? I'd love to see using Redis as the store so it doesn't matter what server gets the callback.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the callback path and the current server-local session store. Evaluate how a Redis-backed store could preserve sessions across restarts and allow callbacks to reach any server. Done means the storage works across server instances and the callback no longer depends on local session state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, redis
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100