I like it, at least more than Zapier and similar pipelines. We have a couple of clients that use our API (geocoding[1]) to enrich their records inside an ETL. Be prepared that some APIs are rate-limited or quota-based, need API keys or other authentication and might return 'over-quota' error messages, never mind latency.
Hi,
thanks for your comment and the link to your Geocoder. I think it's exactly the use case that I faced several times in the past.
I just saw that the Geocoder API is free with certain limitations. If I find some free time, I would like to create an enricher for it. Maybe it can help your clients (and other people of course) to save some time :)
Comments
You have extractor and loader classes, I think the industry term at least in data warehousing is a https://en.wikipedia.org/wiki/Extract,_transform,_load system. Enrichment sounds cool, too.
I like it, at least more than Zapier and similar pipelines. We have a couple of clients that use our API (geocoding[1]) to enrich their records inside an ETL. Be prepared that some APIs are rate-limited or quota-based, need API keys or other authentication and might return 'over-quota' error messages, never mind latency.
[1] https://geocoder.opencagedata.com/
Hi, thanks for your comment and the link to your Geocoder. I think it's exactly the use case that I faced several times in the past.
I just saw that the Geocoder API is free with certain limitations. If I find some free time, I would like to create an enricher for it. Maybe it can help your clients (and other people of course) to save some time :)