Understanding Workflow Execution in Effect with REST API and Runner Communication
hello, i think i'm getting close conceptually to understanding how the cluster, workflow, etc. pieces tie together. is this a correct understanding?
here is an example: a web app that will have a sign up page to create a User. POST /users to my REST API (effect/platform API) will kick off an
that workflow needs to be implemented somewhere, so that lives in the runner service. but the REST API needs to tell the runner to execute the workflow - so is that where creating an RPC API with
also added the shard manager for the sake of the services that would be running, but i'm mostly interested in the REST API <-> Runner communcation pattern re: initiating workflows from a RESTful API endpoint that i want to happen later on in the background (discard: true, no waiting around)
thanks again to everyone's help and code so far as i've gotten to learn more about effect!
here is an example: a web app that will have a sign up page to create a User. POST /users to my REST API (effect/platform API) will kick off an
OnboardingCheckInEmailWorkflow - a workflow that will sleep for 1 day and then send an email to the user.that workflow needs to be implemented somewhere, so that lives in the runner service. but the REST API needs to tell the runner to execute the workflow - so is that where creating an RPC API with
WorkflowProxy.toRpcGroup would be the right way for a client (in this case the REST API) to tell the runner "hey please execute a workflow"?also added the shard manager for the sake of the services that would be running, but i'm mostly interested in the REST API <-> Runner communcation pattern re: initiating workflows from a RESTful API endpoint that i want to happen later on in the background (discard: true, no waiting around)
thanks again to everyone's help and code so far as i've gotten to learn more about effect!
