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
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, ...)?
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
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, ...)?