4 ms·
This seems cool to nerd out to! So thanks for that! But what is the point? Why is this better than making the API call? SQL is for queries, why would I want t
by dennisy 4y ago
This seems cool to nerd out to! So thanks for that!
But what is the point? Why is this better than making the API call?
SQL is for queries, why would I want to do networking with it?
- kiernanmcgowan 4y agoThis ends up being a way to hide an ETL pipeline behind a SQL query. Using this and some materialized views it makes it easy to just pull data in from an external source and just have it in your system. I'm not sure on the value of this for customer facing production systems, but for internal reporting / product analytics this should make it really easy to pull in disparate datasets w/o having to spend eng time to keep each one running.
- rudasn 4y agoPg newbie here, first time I'm reading about this. Super useful for internal tools indeed! Could you point me to any tools or resources on achieving that (pulling data from several external databases into a single one for the purpose of analytics/aggregation)?
- ako 4y agoBecause SQL allows you to better specify what data you're interested in? GraphQL and OData take a similar approach.