Migration File Organization in Multi-Service Architectures

5/10 Medium

Database migration files are placed in frontend repositories by design, creating architectural friction when backends are hosted separately (e.g., AWS Lambda). This leads to unclear ownership of when migrations should run.

SupabaseAWS Lambda
Category
architecture
Workaround
partial
Stage
deploy
Freshness
persistent
Scope
single_lib
Recurring
No
Buyer Type
team
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Supabase for developers in 2025?”4/6/2026

My DB migration files were part of the frontend repo. Traditionally, you want to run db migrations along with backend deployment... In this case, you will end up with a dilemma of where to run migrations!

Created: 4/6/2026Updated: 4/6/2026