3 ms·

Looks cool ! How does it compare to temporal.io in your experience ? I’m evaluating options at my current company, between airflow and temporal.

tchiotludo 5y ago
Temporal.io is a really cool framework for building business process like managing microservice workflow (like paiement workflow: user pay, we call the shipping microservice, the billing microservice, ...) and good fit to handle individual event (lots of individual events). Kestra (and so airflow) is more a workflow manager to handle data pipeline like moving large dataset (batch) between different source and destination, do some transformation inside database (ELT) or with Kestra you are also able to transform the data (ETL) before save it to external systems. This lead Kestra (and so airflow) to have a lot of connectors to differents systems (like SQL, NOSQL, Columns database, Cloud Storage, ...) that is ready to use out of the box. temporal.io, since it's first design to handle microservice (proprietary & internal service) don't have this connector out of the box, and you will need code all this interaction. So my opinion: Building data pipeline interacting with many standard systems will be done easily & quickly with Kestra (or airflow) Handling internal business process of micro service will done easily with temporal.io
jusonchan81 5y ago
Netflix Conductor is great alternative to Temporal. There is a fully managed offering for this as well. The biggest advantage is that it’s quite simple to understand and has great visualization of flows.
hackerdad 5y ago
Have you tried Netflix Conductor (https://github.com/Netflix/conductor https://github.com/Netflix/conductor) - if you are evaluating between Airflow - this could be a great alternative - scales well and gives you option to write your workflows in code as well as config.

3 ms·

Looks cool ! How does it compare to temporal.io in your experience ? I’m evaluating options at my current company, between airflow and temporal.

by crubier 5y ago

tchiotludo 5y ago
Temporal.io is a really cool framework for building business process like managing microservice workflow (like paiement workflow: user pay, we call the shipping microservice, the billing microservice, ...) and good fit to handle individual event (lots of individual events). Kestra (and so airflow) is more a workflow manager to handle data pipeline like moving large dataset (batch) between different source and destination, do some transformation inside database (ELT) or with Kestra you are also able to transform the data (ETL) before save it to external systems. This lead Kestra (and so airflow) to have a lot of connectors to differents systems (like SQL, NOSQL, Columns database, Cloud Storage, ...) that is ready to use out of the box. temporal.io, since it's first design to handle microservice (proprietary & internal service) don't have this connector out of the box, and you will need code all this interaction. So my opinion: Building data pipeline interacting with many standard systems will be done easily & quickly with Kestra (or airflow) Handling internal business process of micro service will done easily with temporal.io
jusonchan81 5y ago
Netflix Conductor is great alternative to Temporal. There is a fully managed offering for this as well. The biggest advantage is that it’s quite simple to understand and has great visualization of flows.
hackerdad 5y ago
Have you tried Netflix Conductor (https://github.com/Netflix/conductor https://github.com/Netflix/conductor) - if you are evaluating between Airflow - this could be a great alternative - scales well and gives you option to write your workflows in code as well as config.