Migrating from Supabase
blog.val.town
Migrating from Supabase
1–10 of 136 posts
Re: Migrating from Supabase
#2Personally, I had a really easy time getting Supabase to work locally. However, we use `dbmate` to manage our migrations instead of built-in Supabase migrations.
Also curious to hear from others on this:
> After a bit of sleuthing, it ended up that Supabase was taking a database backup that took the database fully offline every night, at midnight.
This seems like a terrible design decision if true. Why not just backup via physical or logical replication?
And totally hear the issues here with database resizing and vacuuming and other operations. That stuff is a big pain when it breaks.
Re: Migrating from Supabase
#3The local development & database migration story is Supabase's biggest weakness. I hate having to do migrations live in prod. The admin dashboard is just so much better than any alternative Postgres tooling that it's been worth using despite that. Takes care of the stuff I'd normally be sweating over when writing migrations like nullable fields / FK constraints / JSON formatting for default fields. Would be great if Supabase allowed for a "speculative migration" in its UX where it spit out a file you could use locally to test beforehand.
Re: Migrating from Supabase
#4It definitely needs DB branching.
Re: Migrating from Supabase
#5> Local development was tough
> Unfortunately, we just couldn’t get it to work
Every time I read one of these migration stories, I find myself waiting with baited breath for the part the team couldn't achieve. After finding it, the remainder of the story becomes difficult to read.
It isn't necessarily the team's fault, the developer experience clearly has room for improvement. Props to Val Town for being so honest, it is difficult to do.
Re: Migrating from Supabase
#6> Local development was tough > Unfortunately, we just couldn’t get it to work Every time I read one of these migration stories, I find myself waiting with baited breath for the part the team couldn't achieve. After finding it, the remainder of the story becomes difficult to read. It isn't necessarily the team's fault, the developer experience clearly has room for improvement. Props to Val Town for being so honest, i…
Can you elaborate on why it becomes difficult to read? Was there something obvious they missed?
Re: Migrating from Supabase
#7The options for spinning up CRUD apps (ie, 95% of projects) are still quite miserable.
Re: Migrating from Supabase
#8Curious why have you decided for Drizzle over Kysely.
I was recently exploring the space, and Kysely came on top as a framework with broader adoption.
Re: Migrating from Supabase
#9Curious why have you decided for Drizzle over Kysely. I was recently exploring the space, and Kysely came on top as a framework with broader adoption. https://npmtrends.com/drizzle-orm-vs-kysely
You can actually integrate both as well if you really want to leverage Drizzle for schema building and migrations: https://github.com/drizzle-team/drizzle-orm/tree/main/drizzl...
Re: Migrating from Supabase
#10Echo all the words from the author here, and kudos for being transparent.
I’ve faced exactly the same problems building my new product. But, on the other hand, Supabase was incredibly easy to setup, and meant I could worry about infrastructure later.
Pros and cons like with everything, and always wise to understand the flaws of the tech you’re using.