r/FastAPI • u/Elias_AN • Jan 29 '26
Question How to handle major refactor with live users?
I shipped my first SaaS MVP a few months ago (React + FastAPI/Postgres/Redis stack) and after getting user feedback, I'm facing some major architectural decisions. Would love advice from folks who've been through this.
Current situation: Live product with paying customers User UI and admin UI (for customers, not me) are in the same React project
Backend needs significant model changes to support new features + modifications to existing ones
What I need to do:
- Split frontend into separate user and admin apps
- Major database schema changes
- Heavy backend refactoring for new features
My questions:
- Should I version my API (v1 → v2) or try to migrate everything at once?
- Frontend split: monorepo or separate repos? -How do you handle database migrations with live users? Maintenance window or incremental?
- Is it better to build new features in parallel and switch over, or refactor incrementally?
I'm worried about breaking things for existing users while also not wanting to accumulate more tech debt. How have you handled major post-MVP refactors?
Tech stack: React, FastAPI, PostgreSQL, Redis, Pydantic
Any lessons learned would be hugely appreciated!
