![]() ![]() ![]() So both the reverse ETL and the EL or ETL tools can be, get replaced. Because again, you're not having to kind of sync data in between the source system and the destination system, right? Your source system is your system of record. Right? I would say it breaks reverse ETL redundant and ETL. I mean, so the answer of course is yes and no. So are warehouse-native apps making reverse ETL workflows redundant? ![]() So if you have, PII data, especially on customers, I come from the marketing space. Right? You're not having to rely on these task providers to keep your data safe. And then lastly, from a security and compliance point of view your data is safe in the data warehouse. It shows up in, in the data warehouse or the database it's right there for you to use. Again, on the time saving, you have speed of change, right? You wanted to add a specific field, right? To whatever you're trying to do. You get to bring your own, which is great.Īlso, it's onboarding time, right? Instead of having, again, the same thing with the bring your own data model you don't have to spend days, or not days, months honestly, sometimes years, wrapping out how the data should be modeled in that destination system. 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 many of these warehouse-native cases you get to bring your own data model. 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. So it's single source of truth, of course, as well. ![]() 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? Right, instead of shipping your data out to 10 different SaaS companies. 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. 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. Questions? Check out our primer on warehouse-native apps Right? you can now have those two things, the system of engagement and the system of record separated as well. So, now it's with a separation of compute and storage. Right? And sometimes, companies like Salesforce have traditionally tried to be both the system of record and the system of engagement. 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. You know what they're doing, where they are. 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? 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. Lots of terms for it.īut it honestly, it comes from this idea of the separation of compute and storage. Like this, it's called warehouse-native, warehouse-centric, warehouse first right approach. It's very exciting, right? Lots of new companies are taking this new approach. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |