Hi! I see the terms on the Airbyte website such as "integration" and "sync". Sync to my mind can mean bidirectional: change in place 1 is reflected in place 2 and vice-versa. Can Airbyte be used in a bidirectional capacity or is it strictly source > destination integration in on direction? Thanks!

Hi Steve! There was a discussion recently about this exact topic. Here's its link: https://airbytehq.slack.com/archives/C01A4CAP81L/p1611592039019800?thread_ts=1611555139.016400&cid=C01A4CAP81L

Oh thanks @John (Airbyte) that's 'really useful and looks like good news. Our need is farirly straightforward when it comes to bidirectional sync; basically field in source < --> field in destination so a change in one place makes in to the other. I wonder how Airbyte decides on conflicts, which record is "master" if changes exist in both fields? "most recent wins" would be fine for us.

For the moment, keep in mind that our “sync” are • one direction from source -> destination • incremental in append-only mode (insert, not upsert) • Selection of the destination table is not so easily tuneable as explained by Charles, so it is not do-able to make circular sync (bi-direction) for the moment. But once this matter is worked out, then we can go further in your use case i guess • of course, you are free to create a pipeline from

source -> destination

and then another from

destination -> source

Thanks @Chris (deprecated profile) Doss the concept of going from

Source > Destination

and

Destination > Source

with two pipelines depend on there being connectors being available for me to use in both directions? I notice on the website there appear to be many more Source connectors than there are Destinations. For example having my source as Salesforce and my destination as Postgres is fine, but if I wanted to create a "sync" relationship, there's no Salesforce

destination

for my data to back go in that direction? Perhaps I've misunderstood the website. 😉

You are right, there are more sources than destinations right now with airbyte. And, yes, you would need a salesforce destination… (with some of my ex-coworkers, we had to build such destination with singer for hubspot and other non-warehouse destinations in the past actually. We also had some cyclic syncs of postgres+hubspot+netsuite -> BigQuery -> postgres+hubspot+netsuite)