Welcome <@U06C5FMMCQN> of PipelineWise fame! :wave...
# announcements
d
Welcome @peter_kosztolanyi of PipelineWise fame! waves
I'm looking forward to collaborating on https://gitlab.com/meltano/meltano/-/issues/2364 🙂
a
I love all this collaboration!
e
getting fast-sync into meltano would be great! FWIW, there appears to be a recent third entrant to the singer orchestration space, airbyte. Backstory seems to be a credible founding team raised a seed round in May, then in June (!) realised the idea wasn't viable and have done a hard pivot to orchestrating taps/targets.... from java (?) https://airbyte.io/articles/engineering-thoughts/how-we-can-commoditize-data-integration-pipelines/ https://github.com/airbytehq/airbyte
d
@eamon Thanks for sharing! Airbyte co-founder @john_lafleur actually joined us here on Slack a few weeks ago 🙂 Judging by the Getting Started guide (https://docs.airbyte.io/getting-started-tutorial) and rest of the docs, it looks like they are (so far) focusing on the UI as the primary way of setting up and interacting with pipelines, while we are focusing on the CLI and
meltano.yml
, since we want to support DevOps best practices such as version control, code review, and continuous integration and deployment (CI/CD). I'm looking forward to seeing how Airbyte develops, though, and our UI in response (https://gitlab.com/groups/meltano/-/epics/78)! Either way, the Singer ecosystem and community will benefit from more viable ways to run the taps and targets, and I'm excited to see another team joining us on our common mission to make data integration a commodity!
a
@john_lafleur are you backing the singer framework, or some other approach?
j
Hey all! Thanks for the question @adam_roderick Singer does a good job at creating standalone connectors (although the quality varies a lot). We focus on creating a company wide integration platform. We are using some Singer connectors to bootstrap our project but we’re still figuring out what place it should have over the long term. We will likely maintain some sort of compatibility with their protocol so they can be orchestrated and be usable out-of-the-box in Airbyte.
And we're indeed UI and API first