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.

Sign up for GitHub

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

Jump to bottom

durable workflow data #18

Closed
vroldanbet opened this issue Aug 30, 2023 · 2 comments · Fixed by #34
Closed

durable workflow data #18

vroldanbet opened this issue Aug 30, 2023 · 2 comments · Fixed by #34
Assignees
@ecordell @vroldanbet

Comments

@vroldanbet
Copy link
Contributor

In #16 dual-writes is addressed using a SAGA-like pattern using durable tasks. The state of the workflows is stored in an embedded SQLite which writes to local disk. If the pod is restarted, all state will be lost, which defuses the purposes of the durable task framework.
@vroldanbet
Copy link
Contributor Author

Several options:

  • replace SQLite with whatever database we end up using for permission systems
  • Litestream
  • dqlite.io/
  • LiteFS

@vroldanbet vroldanbet mentioned this issue Sep 19, 2023
Merged
@vroldanbet
Copy link
Contributor Author

Closed via #34
Please read the PR body for the decision on how to make workflow data durable.

I we ever need to switch away from SQLite, I started working on a postgres backend implementation: vroldanbet/go-workflows#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ecordell ecordell

@vroldanbet vroldanbet

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

changes deployment manifest to use statefulset authzed/spicedb-kubeapi-proxy
2 participants
@ecordell @vroldanbet