1. yeah this is nice, making it easier to generate workflows is always good. i think the challenge is always versioning and proper error handling - if the diagram the user sends in doesnt properly model the work done, then you're SOL.
2. (sorry to bring it up but have to ask) how does Diagrid/Dapr compare to Temporal? i browsed your docs but there wasn't much that came up. is Dapr strictly dag based?
1. A user can always go into the generated code and make changes to it. The code generated includes explanations for what each step in the workflow does
2. Dapr has 9 APIs, one of which is Workflows which indeed competes with Temporal. Dapr Workflows isn't DAG based, it's code-first. This tool allows you to start with an external representation
Comments
1. yeah this is nice, making it easier to generate workflows is always good. i think the challenge is always versioning and proper error handling - if the diagram the user sends in doesnt properly model the work done, then you're SOL.
2. (sorry to bring it up but have to ask) how does Diagrid/Dapr compare to Temporal? i browsed your docs but there wasn't much that came up. is Dapr strictly dag based?
1. A user can always go into the generated code and make changes to it. The code generated includes explanations for what each step in the workflow does
2. Dapr has 9 APIs, one of which is Workflows which indeed competes with Temporal. Dapr Workflows isn't DAG based, it's code-first. This tool allows you to start with an external representation