Warehouse-native Apps w/ Luke from MessageGears databeats

→ Link to the series.What is a warehouse-native app and what are its benefits over a managed app?Luke Ambrosetti (who was at MessageGears and is now at Snowflake) not only has first-hand experience but is also deeply knowledgeable and passionate about the warehouse-native architecture. I learned a bunch from his answers and am pretty sure you will too.Let’s dive in:Q. What is a Warehouse-native app?So a Warehouse-native app is effectively a SaaS application that connects directly to the data warehouse and is doing a data-intensive process for you.Q. Are connected apps or data apps the same as warehouse-native apps?Kind of, it depends on who you ask, right? The definition of a connected app or a data app could be very different, to people. And in my view, I'm seeing connected app as kind of a good definition of a warehouse-native SaaS app. Whereas data app could be it could be a SAS, it could be that thing, but maybe data app is actually a larger term that incorporates, maybe an internal app that you create at your, at the company you work for, could be a data app. Right? It doesn't have to be some sort of external tool that you, you buy and or useQ. What is leading to such a paradigm shift in the way B2B SaaS tools are being built?It's very exciting, right? Lots of new companies are taking this new approach. Like this, it's called warehouse-native, warehouse-centric, warehouse first right approach. Lots of terms for it.But it honestly, it comes from this idea of the separation of compute and storage. Right? And then specifically kind of in the industry that I work in, which is more marketing, is this idea of that I've seen, it explained very well, is this idea of the the separation of the system of engagement. Right? Of how you're reaching out to, in this case the marketing's case, your customers, right? And the system of record of, and where what is the state of that customer?You know what they're doing, where they are. the Customer 360 as it's called. So with those two things separated, or traditionally, I should say you've had to get your data to your system, whatever your system of engagement is. Right? And sometimes, companies like Salesforce have traditionally tried to be both the system of record and the system of engagement. So, now it's with a separation of compute and storage. Right? you can now have those two things, the system of engagement and the system of record separated as well.Questions? Check out our primer on warehouse-native appsQ. So besides cost savings, what are some key benefits of using a warehouse-native engagement tool over a traditional one?So yeah, and again the cost savings aspect right here is the idea that you don't have to sync that data right to whatever, your other platform is of where you want to, do either that that in whether it's, if it's marketing, it's engagement, maybe it's analytics, you don't have to sync that data there either whatever it might be. Right?So that's where the cost savings comes from, but there are so many other, benefits as well right? So it's, you have few data silos, you do it this way. Right, instead of shipping your data out to 10 different SaaS companies. If all 10 could connect your data warehouse and use that system of record, you don't have to duplicate data, I guess, is you know what I'm trying to say, right?So it's single source of truth, of course, as well. And that's gonna be better, especially for like things like data absorbability or analytics, right? Being able to attribute different events that happen, back to again where you have all of your data setting, instead of it, again, being in a silo you have to then extract with an ETL tool. You get to bring many of these warehouse-native cases you get to bring your own data model. So instead of having to force your data model into kind of how they view the world or how they think your data should be modeled. You get to bring your own, which is great.Also, it's onboarding time, right? Instead of hav