PolicyEngine / PolicyEngine/policyengine-api
`local_database` violates recommended stateless design
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 22
Description
If I understand the current design correctly, then local_database is stored on the instance in gcloud. However, gcloud warns that
frequent instance restarts can occur without warning [...] Your app should be "stateless" so that nothing is stored on the instance.
Contributor guide
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
The issue identifies local_database and the gcloud deployment; first inspect where local_database is created and persisted, then compare that behavior with the linked App Engine instance-uptime guidance. The issue names no file, test, or target storage, so confirm the intended approach with maintainers. Done when the API no longer depends on instance-local state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- backend, cloud, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100