3 ms·
I'm surprised it doesn't mention selling "mash ups". I imagine there's some opportunities to talking to one service and decorating it with associated data from
by tyingq 4y ago
I'm surprised it doesn't mention selling "mash ups". I imagine there's some opportunities to talking to one service and decorating it with associated data from another service. Or even just better thought out aggregated services from one provider. I suppose then it's engineering, but the kind of thing an out of the box api proxy could do with just configuration.
A proxy would also open up opportunities like serving cached responses for more static calls, which would raise your margin.
- judge2020 4y ago> I suppose then it's engineering Careful, that’s supposed to stay a secret! https://news.ycombinator.com/item?id=31226100 https://news.ycombinator.com/item?id=31226100
- dc-programmer 4y agoI was exposed to the idea of reverse ETL recently. The essence of the paradigm is to have a workflow that retrieves data from your SaaS APIs, transforms and enriches it, and then ingests this data into other SaaS providers in order to automate various backend workflows. In a way it’s similar to a gateway in that you are composing different backend targets. Although it might just be a marketing neologism describing middleware.
- maxerickson 4y agoI continue not to understand the "reverse" in that name. Like if you aren't already doing "transform", you probably aren't reversing it.
- dc-programmer 4y agoI’ll concede that the E, the T, and the L are the only operations I see in this model
- renewiltord 4y agoTraditional ETL tools focused on getting data out of services and into a few places like a relational DB, S3, or some other such aggregated storage so they were read-only from services and read/write to DBs. Reverse ETL is marketing to differentiate to the customer that you're pushing data into services as well, so that it's read/write to all. Of course the concept is amusing to someone talking about ETL, but the market moved at some point to refer to the first functionality as ETL and so this is just a change to differentiate.
- ethbr0 4y agoParent didn't chose the best starting place to illustrate. Typically, reverse ETL starts with "all of my data is already in an EDW" and goes to "I want to push it to my various app systems." Canonical example: pushing system of record information to Salesforce to speed and enrich the sales cycle. https://hightouch.io/blog/reverse-etl/ https://hightouch.io/blog/reverse-etl/
- dc-programmer 4y agoMy bad. My introduction to the topic was through the lens of different use cases
- ethbr0 4y agoNp! Wasn't intended as a slight. We all come into new things the way we do, rarely via the textbook definition (which typically doesn't even exist when we're first doing it!).
- maxerickson 4y agoStill, my understanding is that ETL predates the whole "data warehouse" thing. Like "extract" isn't any more specific than a source and "load" isn't anything more specific than a destination.
- dc-programmer 4y agoSomeone should create a startup that offers SaaS attribute entity resolution in Log4j