3 ms·
Whether enterprise or not, the criticism is still fair: the value proposition needs to be super clear. I’m missing this. Your comments make it a bit more clear
by stingraycharles 3y ago
Whether enterprise or not, the criticism is still fair: the value proposition needs to be super clear. I’m missing this.
Your comments make it a bit more clear, but the big question (as an Airflow user) I have is: why would I want to migrate?
A big question for an enterprise customer is typically: will I save money with this? In developer productivity, in resource costs, or something else? Can you unlock new things that were previously not possible?
I wish you guys the best.
- jordanbeiber 3y agoQuestion is - what are you using airflow for? My experience with airflow have been in data ETL, and if so you are not the target for something like windmill. The target would most likely be automating HR, Finance and IT workflows and tearing down the shadow IT web of crazy integrations taking place at every larger organization I’ve ever experienced. We’re talking “new hire” workflow for example, which at my current employer is about 25 activities in a workflow. All assets have to be lifecycle managed in an enterprise and automated workflows will help you scale that. Far too many enterprises have a lot of people shuffle excel files and emails around to fulfill processes and workflows. Airflow is a beast imho and usually not used in the same niche IME.
- cgio 3y agoJust guessing with no background experience on windmill, maybe to support reactive workflows. Airflow does not have a good proposition on that front. Sensors are a workaround and not performant.