`Match for a specific use case` Hello there :wave:...
# ask-community-for-troubleshooting
p
Match for a specific use case
Hello there 👋, I wanted to ask you if Airbyte was a good option for a particular use-case: not as an ETL but as a RETL 🧐. I explain: we developed a lot of data-models via dbt in our DataWarehouse, Snowflake, and we unload them to a PostgreSQL instance in order to expose them to our end-users (Snowflake is OLAP oriented and not fast-enough for end-users queries, thus the need to unload them to Postgres) ️. So our use-case is to keep a perfect sync between our Snowflake tables and our Postgres tables 🔄. By perfect sync, I mean having all the fields needed, a regular incremental replication and handling of deleted rows We already set-up primary key in our Snowflake tables, as well as a "meta-field" with the last update date of the row 👍. Thanks a lot! 🙏
1
a
Hi @Pierre CORBEL, yes, I confirm that Airbyte would be a good fit for this use case. We have a source connector for Snowflake and a destination connector for Postgres, and we support incremental replication. You should give Airbyte a try.
p
Thanks a lot 👍
One other question @Augustin Lafanechere (Airbyte), Is it possible to run an Airbyte EL job directly in a container? i.e. without having to setup the server, worker, scheduler, etc? I have in mind a Singer-like container with as an entrypoint that could be like:
airbyte source --conf foo | airbyte destination --config bar