Pioreactor / Pioreactor/pioreactor
Continuously backup the database instead of batch backups
Open
Nobody has claimed this yet.
future
plugins
sql / database
- Dominant language
- Python
- Stars
- 149
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Consider something like litestream
Pros:
- no need for heavy backup jobs (#81)
- always up to date data replicas, instead of every N days
- delete our own internal backup code
Cons:
- how does litestream deal with a replica being unavailable?
- more cpu work upfront during an experiment
- more overhead during an experiment
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 locating the existing internal batch backup code and reviewing issue #81. Evaluate whether Litestream can provide continuously updated replicas when a replica is unavailable, including the stated CPU and overhead costs. Done means replacing the batch approach with continuous backups and removing the internal backup code.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100