stripe-sync-engine VS airbyte

For everyone in this thread that use ORM for migrations, which seems like rather heavy handed approach, have a look at https://github.com/supabase/stripe-sync-engine/blob/main/src/utils/migrate.ts which is how you can easily implement migrations without all the ORM overhead/bullshit.

Stripe-Supabase Sync Engine: syncing the stripe database to supabase would’ve been nice but also would’ve been a lot of unnessary extra work (I’ll just use stripe webhooks instead). Also, I needed to spin up something to host that and I wasn’t willing to do that.

I've heard good things about Supabase, but I haven't used it myself. If you're in a position to deploy the DBMS and backend software yourself, you could consider setting up PostgreSQL and a gRPC server service yourself. You can even write the server service in Dart.

For those who need a clickable link to the project: https://supabase.com/

Supabase account

If I want to build micro-saas then are one options from above feasible? or should I go with supabase? https://supabase.com/

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