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

Sagas support #7

Open
roblaszczak opened this issue Nov 18, 2018 · 2 comments
Open

Sagas support #7

roblaszczak opened this issue Nov 18, 2018 · 2 comments
Labels
enhancement New feature or request L large issue module: components

Comments

@roblaszczak
Copy link
Member

No description provided.

@roblaszczak roblaszczak added the L large issue label Sep 16, 2019
@vikstrous
Copy link

What are your thoughts on how sagas should work with watermill? It seems to me that it's pretty simple to implement a choreograpy based saga using the existing features of watermill. To implement an orchestration based saga, wouldn't you just not use watermill at all? Doesn't it make more sense to implement an orchestration based saga by just creating a service that stores its state in a database (or even filesystem) and logs its progress there without the need for events or pub/sub or anything fancy?

@roblaszczak
Copy link
Member Author

@czeslavo prepared a pretty nice example of Process Manager implementation with Watermill here: https://github.com/czeslavo/process-manager. It's not Saga, but it's pretty similar and with some additions, you may implement saga in a pretty simple way.

Anyway, it would be good to have some tooling in Watermill to support it more out-of-the-box - and this is the long term plan ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request L large issue module: components
Projects
None yet
Development

No branches or pull requests

2 participants