Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Very cool! I think concurrency conflicts can be solved using github actions... (to an extent) :) #2

Open
Skparab1 opened this issue Apr 10, 2022 · 1 comment

Comments

@Skparab1
Copy link

Wow very cool analysis! I was inspired by this idea and created something similar that uses the same read method, but to write, it uses a machine account that sends an issue (with data) to the repo. This triggers a github action, which takes the issue data and writes it back to the json file. Even if multiple users attempt to write at the same time, you can make the github action retry committing to the repo if it fails (which will happen if two actions try to write at the same time). This effectively solves the problem of concurrent conflicts (to an extent, because if there are enough write requests at the same time then the action will stop retrying, and the data will be lost). However, it is much slower than just committing, and isn't that useful when trying to use github as a fast database. Anyway, I think this idea is very cool, and you can see my repo here and my implementation here. I also believe that you can make github actions merge and delete branches, instead of doing it manually, so that would make the process more automated.

Thanks! :)

@Skparab1
Copy link
Author

Anyway, idk if ur still maintaining this repo, but very cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant