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

Only store references to events/payloads for backends #39

Closed
cschleiden opened this issue Apr 11, 2022 · 1 comment · Fixed by #275
Closed

Only store references to events/payloads for backends #39

cschleiden opened this issue Apr 11, 2022 · 1 comment · Fixed by #275
Assignees
@cschleiden
Labels
backend:mysql backend:redis backend:sqlite Performance

Comments

@cschleiden
Copy link
Owner

cschleiden commented Apr 11, 2022 •
edited
Loading

SQL backends

Instead of duplicating events in the history and pending_events table, events should be stored in a single events table. history and pending_events should contain only references to the events.

Redis backend

  • Separate payloads into a separate hash?
@cschleiden cschleiden changed the title Only store references to events for SQL backends Only store references to events for backends Jun 17, 2022
@cschleiden cschleiden changed the title Only store references to events for backends Only store references to events/payloads for backends Mar 1, 2023
@cschleiden cschleiden self-assigned this Apr 4, 2023
@cschleiden
Copy link
Owner Author

Experimenting in #181

This was referenced Nov 4, 2023
Merged
Merged
@cschleiden cschleiden mentioned this issue Nov 11, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cschleiden cschleiden

Labels
backend:mysql backend:redis backend:sqlite Performance
Projects
go-workflows backlog
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move mysql attributes to separate table cschleiden/go-workflows
1 participant
@cschleiden