How to start with data and save your resources - with Jonas Thordal from Weld
Arkiverad serie ("Inaktivt flöde" status)
When? This feed was archived on September 28, 2024 20:08 (). Last successful fetch was on February 26, 2024 18:24 ()
Why? Inaktivt flöde status. Våra servar kunde inte hämta ett giltigt podcast-flöde under en längre period.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 334376947 series 3332241
Listen to my conversation with Jonas from Weld to learn more about deciding on a data stack, the benefits of an integrated platform, and how to start with data in your company.
It’s so much fun to build your data stack bundle by combining 2, then 5, then ten different tools. The significant promise of best-of-breed is that you shop for the best solutions and just connect them with the promise that you can always swap solutions when something better comes up. That’s the theory.
So why would you use a platform that is doing 4-5 things that single tools could do for you as well?
- You definitely save time by getting everything running
- You don’t have to learn four tools, just one
- You just make one contract/subscription instead of 4
These can be compelling reasons.
But in my conversation with Jonas from Weld, I learned about a significant benefit that is not obvious in the first place. The meta layer.
What is the meta layer? An integrated platform knows everything from ingesting, modeling, storing, and activating. Because it all happens in one place, they can run monitoring on top and do deep lineage. They simply know how data moves from a to b to c. They can even know how much costs you generate at the moment in your cloud setup and can advise you on savings.
This is an immense benefit over best-of-breed solutions where you have to create the meta layer yourself (or believe that data ops, monitoring, or catalog tools do it for you).
9 episoder