Hacker News new | ask | show | jobs
by teraku 2165 days ago
This looks awesome, but I don't understand what this has that airflow, prefect or luigi don't have?
2 comments

Scale, interactivity, and durability are certainly part of this discussion. You can use Cadence/Temporal for purposes you just really couldn't use Airflow for. For instance, you could implement this entire actor-based auction example from Akka with Cadence/Temporal https://doc.akka.io/docs/akka-enhancements/current/persisten... There is absolutely no way you could do that with Airflow.

To understand why Cadence is so useful, you have to go a bit beyond the traditional ETL scheduling usages IMO.

In SWF/Durable Functions/Cadence/Temporal, The entire workflow is defined as (deterministic) code, which is orchestrated by the engine.
As as opposed to... having undeterministic code? Workflow as code is also the theme of airflow, luigi and prefect.
With Temporal/Cadence you write (mostly) plain code to implement your business logic rather than using code to define DAGs.

This discussion has more on Airflow vs Cadence: https://news.ycombinator.com/item?id=19732447