stripe-sync-engine VS stripe-firebase-extensions

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/

Stripe was the most difficult and finicky aspect of the migration. Within firebase, I used the stripe firebase extension to manage all the stripe components. It took care of a lot of the implementation work so I had no idea how to approach this when I first started. I bounced between different ideas like bi-directional sync of the subscription tier within firebase, but eventually I settled upon using Stripe as my single source of truth. Although it’d be more involved, I knew it’d make fully cutting Firebase out of Fleeting Notes easier down the road. Here are the migration steps I settled upon:

In this example, we are going to use the Stripe Payment Extension updates, which will allow an enhancement of the Stripe Webhook events. In this example, we are going to focus on when a product has been created.