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

Workflow State #27

Open
pedramha opened this issue Dec 7, 2018 · 1 comment
Open

Workflow State #27

pedramha opened this issue Dec 7, 2018 · 1 comment
Labels

Comments

@pedramha
Copy link

pedramha commented Dec 7, 2018

Hi,
I would like to know if Toki saves the workflow state under the hood.
Does it use a message broker(pub-sub) or is it pure request response?

@WesTyler
Copy link
Member

WesTyler commented Dec 7, 2018

Hi there

saves the workflow state under the hood

if I'm understanding the question correctly, no it does not. Any data associated with an orchestrated action is held in memory in the context of the single request and is GC'ed after the response.

Does it use a message broker(pub-sub) or is it pure request response?

The core api contract and functionality is pure http request/response. The being said, the plugin nature of the orchestration means you can integrate with a pub/sub hook or anything you'd like as part of the orchestrated workflow.

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

No branches or pull requests

2 participants