-
Notifications
You must be signed in to change notification settings - Fork 3
2.0 Migration Strat Plan
shicks255 edited this page Mar 5, 2022
·
5 revisions
Currently, RecipeBook is a react front end, making calls to a spring backend.
The new plan is to use a node/express backend with graphql (and initially rest) calls.
To do things piecemeal, we'll need to do something like
Phase 1: Spin up new express backend with rest api
Phase 2: Migrate the react fetch calls to use the new express backend 1 endpoint at a time
Phase 3: Create graphql endpoints in express backend.
Phase 4: Migrate the fetch calls in frontend to use graphql
Phase 5: Remove spring backend after all verification is complete We could remove the express rest api, but i don't see any harm in keeping it in place as it is.
Responsibilities during this
Steven:
- New node/express backend with graphql layer
- Use graphql client when graphql backend is ready
Eric:
- Change frontend to point to new rest api when ready
- Migrate DB to supabase
- Work on using supabase for auth