Thanks for the mention Benjamin! We very much agree!
Our LI post is a challenge of the status quo. Both terms are vendor driven and each user camp only hears their side. The 2 stacks have largely different use cases and application with some intersection. The future is not one thing, but many of the MDS vendors already belong in the past. For example on data transfer, you can use a paid tool for SQL copy, and it will be slow and expensive, or you could set up an open source pipeline that works 10x faster with 200x less cost.
Thank you so much for the mention, Ben 🙏 it means a lot man
You're welcome!!
Thanks for the mention Benjamin! We very much agree!
Our LI post is a challenge of the status quo. Both terms are vendor driven and each user camp only hears their side. The 2 stacks have largely different use cases and application with some intersection. The future is not one thing, but many of the MDS vendors already belong in the past. For example on data transfer, you can use a paid tool for SQL copy, and it will be slow and expensive, or you could set up an open source pipeline that works 10x faster with 200x less cost.
example: https://dlthub.com/blog/replacing-saas-elt
So if you just follow the discussion of one side, you will miss out on the benefits of the other.
dlt is unique in that it both leverages the composable stack under the hood, enabling amazing speed gains, while fitting well into the MDS.
Check out how we get 30x speed gains using arrow under the hood, and also why we use it, and why we don't use it.
At the same time, our airflow, dagster and dbt integrations are the most popular extensions.
https://dlthub.com/blog/how-dlt-uses-apache-arrow
https://dlthub.com/blog/dlt-arrow-loading