Sam Sussman
Sam Sussman
closes #97 * ~~Cancel~~, Complete, or Fail any activity from event handler, activity, api, or workflow using it's activity token. * Cancel, ~~Complete, or Fail~~ an activity reference the workflow...
One other thing I'd add is that I like to separate out persistent resources from service logic. If we could have separate construct instantiations to publish ephemeral vs stateful resources...
Should be able to cancel a running workflow execution 1. Fail the workflow with CancelationError 2. cancel all running activities (by the activity looking up the workflow status during heartbeat)...
* workflow.startExecution * Needs to fail or support being called from a workflow * activity.complete * Needs to fail or support being called from a workflow (handled in #101 )
The activity token is currently base64 JSON object which contains the execution id and seq number of the activity. This has a few issues: 1. not secure - could be...
This reminds me - we should make naming a service mandatory instead of defaulting to the long Construct.node.addr. _Originally posted by @sam-goodwin in https://github.com/functionless/eventual/pull/295#discussion_r1119590812_
Data returned from activities and workflows may be larger than can we stored in dynamo and sqs. * Save values into s3, dynamo, or inline using an abstracted client based...
Using #272 Move the service to service subscribe and publish behaviors to the service layer. ```ts const serviceB: Service = service.from(...); // put service B events into service A bus...
A developer should have control over which events are published outside of the service (service to service subscribe). When a developer uses service to service subscription, the subscribed events should...