How to build a custom data connector in 2 hours
airbyte.io
airbyte.io
I was excited.
Pretty thrilled with how fast these guys have been going honestly. Only picked up their stuff a few months ago and there are already more and better connectors today than there were back then.
I’ve been slowly moving over my error prone sync scripts to my Airbyte instance. Life is already better.
We built something similar for on-premise data sources, in Clojure. https://basil.net
I fired up an EC2 instance, docker-compose'd up, added the initial few syncs and then let people just add their own.
Mostly without trouble since then, though I'm running an old version as a result of the fire-and-forget.
(edit: also, text me on Keybase or email me since I don't get notifications for responses here)
Airbyte comes also with ~70 connectors. So if we already support the destination you want, you can only build the source connector that we might not support as well. Our goal is support 200 connectors by the end of the year and address the long tail of integrations in 2022 :).
That being said, I’ve got a fun project in mind which I may find a use case for this. I’ll give it a shot.
For data engineers, the objectives is to help them empower other roles to be data fluent and have the freedom to move data without bugging data engineers
I might have a project coming up to build a semi-analytics solution where you would obviously want to allow the users to easily connect to their data sources, and Airbyte looks like it might be a good fit for that (for now my rough idea was to build some plumbing around Singer taps). Are you aware of any users that use it for such purposes and are there any specific pitfalls too look out for there?