This application, coupled with a sync service (e.g. rclone) can be used to dump RethinkDB database data to archive and subsequently uploaded to the cloud (e.g. Dropbox). There are a few questions that remain:
- How should a dump/sync be initated?
- How should each dump/sync be handled?
- How should the dump/sync data be managed?
Initiate a dump/sync
A) cron job
B) client requests through web service (currently implemented)
C) listen to DB
Handle a dump/sync
A) Each request handled immediately
B) Delayed (e.g. 1 hour), additional requests ignored; accept post-submit changes immediately
Handle a dump/sync data
A) Keep everything
B) Clean up the server dumps
C) Clean up the server dumps and mirror everything on cloud
This application, coupled with a sync service (e.g. rclone) can be used to dump RethinkDB database data to archive and subsequently uploaded to the cloud (e.g. Dropbox). There are a few questions that remain:
Initiate a dump/sync
A)
cron jobB) client requests through web service (currently implemented)
C) listen to DB
Handle a dump/sync
A)
Each request handled immediatelyB) Delayed (e.g. 1 hour), additional requests ignored; accept post-submit changes immediately
Handle a dump/sync data
A) Keep everything
B)
Clean up the server dumpsC)
Clean up the server dumps and mirror everything on cloud