typhoon-orchestrator VS astro

I have my own opinion on Airflow's pain points and created Typhoon Orchestrator (https://github.com/typhoon-data-org/typhoon-orchestrator) to solve them. It doesn't have many stars yet but I've used it to create some pipelines for medium sized companies in a few days, and they've been running for over a year without issues.

In particular I transpile to Airflow code (can also deploy to Lambda) because I think it's still the most robust and well supported "runtime", I just don't think the developer experience is that good.

Typhoon Orchestrator This is a framework that I designed to help fix some of the pain points of Airflow so that I could build test and deploy pipelines faster. You could skip this step but if you want more info check here.

I am also collaborating on an open source tool called Typhoon Orchestrator (repo). It aims to make composing airflow data pipelines simple and quite quick. Putting pipeline steps together like lego.

The project (https://github.com/typhoon-data-org/typhoon-orchestrator) doesn't have many stars yet but I have deployed it on a medium sized hotel chain for several data sources with a similar use case to yours and it's been working for over a year with no intervention. If you decide to pursue this option I'd be willing to provide provide some support free of charge (feel free to PM me).

Typhoon Orchestrator is a great way to deploy ETL workflow on AWS Lambda. In this tutorial we intend to show how easy to use and versatile it is by deploying code to Lambda that gets a random joke from https://jokeapi.dev once a day and sends it to your telegram group.

I think there's space for an open source library that can help with what you described. We originally created https://github.com/typhoon-data-org/typhoon-orchestrator to orchestrate ETL workflows, which would be a superset of the use cases you described. Our next goal is to allow deployment to AWS lambda which can be a good compromise between getting locked in with SAAS and hosting your own infrastructure.

Also check out Zappa's scheduled tasks that have a similar goal and inspired our library.

What I would suggest is if you want an "Airflow 3.0" feel you check out the Astro SDK. My team and I basically spent a year and a half rewriting the Airflow DAG writing experience from the ground up. Completely different feel, highly scalable SQL/python/spark (soon) workflows that basically feel like native python. Way easier to test as well. You can pass dataframes into SQL queries, load data from any supported source to any supported warehouse, and things like lineage are natively supported :)