Hi everyone 🙂 Having used Fivetran for the past few months while building an MVP, we’re migrating to Meltano to reduce our costs. Now the decision is between using Airflow or Dagster for orchestration. If it wasn’t for the Meltano docs mentioning their support for Airflow out of the box, I wouldn’t be hesitant choosing Dagster. My question is whether the support and documentation is better for Airflow or Dagster? What Meltano-specific reason is there for choosing one orchestrator/utility over another?

Meltano supports Apache Airflow out of the box, but can be used with any tool capable of reading the output of

meltano schedule list --format=json

and executing each pipeline’s

meltano run

command on a schedule.

Thanks for the support!

Hi @Benjamin Scholtz - hey, really sorry, I just got pinger here by somebody else and I see your note from two months back.. My bad. The quick and dirty is that Airflow was the default and the incumbent on the Orchestration front, and Meltano reasonably optimized for that orchestrator. There is a

<https://github.com/quantile-development/dagster-meltano|dagster-meltano>

integration. I wrote up a blogpost last year on how to use the integration here: https://dagster.io/blog/dagster-meltano-integration-tutorial This said, Meltano is ont on the roadmap for Dagster’s embedded elt functionality which is adopting dlt and Sling.