Dedicated orchestration tools like Airflow matter only when you need highly isolated, reliable orchestration for specific workloads. For most data work, native features in Snowflake or MotherDuck do the job without adding unnecessary complexity.
Chapters
It's still, it's something you did. It's like under, under the hood. Is it going to be a completely separate tool? Um, I mean, even looking at Orchestra or Katya, how they're like morphing and changing. No, I don't think, I don't think so. I think there are actually times where you should, you do want it to be completely separate. Usually those are like when you want really isolated, really specific, high reliable tools. And I think that's like really important. Yeah. Like, get simple orchestration. But I mean, ultimately, in a vast majority of data work, is like, does this deliver value, right? Do I need to have this completely separate Airflow tool to move all these things? Or does Snowflake's orchestration or ingestion patterns in MotherDuck solve my problem, right? Like, majority of the time it's yes. It's like, You're kind of like over-indexing on toys and then not really valuing. We talked about this the whole time really between you and I. We're like, do you need another tool? Yeah. And does your data platform support it?