[Task]: Gateway Controller should always run with persistence enabled.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/UX (User experience, flows, usability, clarity)
Description
In Memory Store only mode does not work properly when gateway controller running in multiple replicas. Given that Gateway Controller always have a Database (SQLite by default) there is no need for in memory store. And that would reduce the complexity.
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
Search the repository for the Gateway Controller’s in-memory store and persistence configuration, then trace how SQLite is initialized when multiple replicas run. Done means the controller consistently uses persistence rather than memory-only mode, with the relevant multi-replica behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- api, backend, databases
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100