←back to thread

Show HN: Turn any workflow diagram into compilable, running and stateful code

(workflows.diagrid.io)
109 points yaronsc | 1 comments | 14 May 25 17:52 UTC | HN request time: 0s | source

Hi HN folks, I'm a co-creator of the Dapr CNCF project and co-founder of Diagrid. Today we announced a free-to-use web app that takes any form of workflow diagram (UML, BPMN, scribble in your favorite drawing tool or even on paper) and generates code that runs in any IDE and that can be deployed to Kubernetes and other container based systems, based on Dapr's durable execution workflow engine. This essentially allows you to run durable workflows in minutes and leaves out the guesswork for how to structure, code and optimize a code-first workflow app. I'm happy for you to give this a try and provide feedback!
Show context
Rexxar ◴[18 May 25 20:09 UTC] No.44023977[source]▶
What is the difference with tools like Camunda (for BPMN) for example ?
replies(1): >>44025054 #
yaronsc ◴[18 May 25 23:24 UTC] No.44025054[source]▶
Dapr is a code-first workflow engine that doesn't require a DSL language and includes many other integration points like pub/sub, service discovery and more. It also runs and deploys natively on K8s
replies(1): >>44031041 #
1. fock ◴[19 May 25 15:43 UTC] No.44031041[source]▶
So for workflows it's like Airflow, Brigade or hatchet or ...? How do workflows integrate with k8s (ressources, ...)? Camunda can also deploy natively on k8s. However you still develop apps for Camunda and it seems like dapr is no different there? Why is it in CNCF if it doesn't provide a way to build a workflow out of k8s-native artifacts (PVs, Deployments, Jobs, ...)?