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

Apply state changes when writing/reading events #6171

Closed
saig0 opened this issue Jan 26, 2021 · 0 comments · Fixed by #6250
Closed

Apply state changes when writing/reading events #6171

saig0 opened this issue Jan 26, 2021 · 0 comments · Fixed by #6250
Assignees
Labels
kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. scope/broker Marks an issue or PR to appear in the broker section of the changelog

Comments

@saig0
Copy link
Member

saig0 commented Jan 26, 2021

Description

When migrating the stream processors, we need to make sure that all state changes are reflected by events. We want to extract the state changes in the processors/behaviors into a StateWriter that writes an event and apply the state change. The same logic is called on replay to restore the state.

  • create the basic structure (i.e. StateWriter, EventApplier) that can be used by the processors and for replay

ZEP - Event Sourcing - Implementation

Reference:

@saig0 saig0 added kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. scope/broker Marks an issue or PR to appear in the broker section of the changelog Status: Ready labels Jan 26, 2021
@saig0 saig0 added this to the Updatable Workflow Engine milestone Jan 26, 2021
@zeebe-bors zeebe-bors bot closed this as completed in b76f811 Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. scope/broker Marks an issue or PR to appear in the broker section of the changelog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants