buildbuddy VS airbyte

BuildBuddy (YC W20) | Engineering | Remote, Bay Area | Full-Time

BuildBuddy was founded to give anyone a "Google-style" development environment in minutes. Today we're solving a small piece of this problem with an open-core remote build execution platform for Bazel - but our ambitions are much larger. Our mission is to take the world-class engineering tools that are only available to employees of large companies and make them available to everyone. Check it out at: https://buildbuddy.io/

Come join us and shape the future of how engineers build and test software! You’ll write and ship open-source code, own production systems used every day by 1000s of engineers at big companies, and help us shape the future of the product. You'll work with and learn from a team that's built software at both successful startups and FAANG companies. Your skillset will grow and you'll join a team excited to solve problems in the developer tool space.

Our tech stack is simple, stable, scalable: Golang, Redis, MySQL, Protobuf, React, Typescript.

Sr. SWE: https://www.buildbuddy.io/jobs/senior-software-engineer

Sr. SRE: https://www.buildbuddy.io/jobs/senior-site-reliability-engin...

SE: https://www.buildbuddy.io/jobs/solutions-engineer

Don't see a perfect fit but still interested? Great, we still want to hear from you! Email us at [email protected]

I'l also give a shout-out to Airbyte (https://airbyte.com/), with which I've had some limited success with integrating Salesforce to a local database. The particular pull for Airbyte is that we can self-host the open source version, rather than pay Fivetran a significant sum to do this for us.

It's an immature tool, so I don't yet know that I can claim we've spent _less_ than Fivetran on the additional engineering and ops time, but it feels like it has potential to do so once stabilized.

Link to GitHub -->

When it says "available in open source", is that under the main airbyte repo's licensing [1], hence primarily licensed under the Elastic License v2 and therefore not typically considered open source by many?

Airbyte has previous of advertising their offering as open source while not really being as per the OSD[2]. This has been raised with them previously but without response [3][4]. They've also been extending their use of ELv2, recently moving many of their existing MIT licensed connectors to be ELv2 [5].

[1] https://github.com/airbytehq/airbyte/blob/master/LICENSE

As possible solution, I can suggest Airbyte(https://airbyte.com/). it's more performant than generic python script.

Airbyte, an open-source data integration engine that offers hundreds of connectors with data warehouses and databases, has gained popularity for its seamless integration and data syncing capabilities. Xata's integration with Airbyte offers a streamlined data ingestion process from any Airbyte input source directly into your Xata database.

You can try and contribute some new connectors/operators for workflow managers like Airflow or Airbyte