Hi folks, I’m learning dagster and prefect for MLOps and data engineering. While two frameworks have several advantages over AirFlow such as dynamic flow or python functional API in common, I am not sure about the difference between dagster and prefect. Some people say dagster is data-driven and prefect is task-driven, but I am not sure how does this difference lead to differences of concrete appropriate usecases. Could anyone explain advantages (and disadvantages) of dagster over prefect??

i'd agree with @Romain. In my trials, the other thing Dagster offers is a very clear path to CI/CD pipelines. It's possible I missed it with Prefect, but the out-of-the-box github actions for dagster cloud were chefkiss , and it is also very nice to be able to develop locally with a complete setup, whereas deploying with Prefect's hybrid architecture seemed somewhat less clean.