Storage architecture

[Karina5005]

There are several options for saving data for future restore:

1. Replicate the entire structure provided by the GitHub API, keeping all the information returned as a response in full.

   Pros:

   • Ease of compatibility with other tools. Everyone understands what structure the recovery program will expect, so you can use a backup from another tool.
   • API changes are easier to maintain

   Cons:

   • Saving a lot of redundant information

2. Creating custom storage structure
   Proc:

   • Minimum memory consumption. We store only what is really needed to restore
   • Easier to implement restore

   Cons:

   • Strong connection between backup, restore, and GitHub API. Changes to any part will require changes to the rest.

3. Replicate the structure of the GitHub API, but throw out the fields that are not used for restore.

   Pros:

   • Ease of compatibility with other tools. Everyone understands what structure the recovery program will expect, so you can use a backup from another tool.
   • Almost minimum memory consumption. Due to the more complex structure, store a small amount of redundant information
   • Easier to implement restore

   Cons:
   ???