Engineering Challenges
Designing a normalized relational schema in Prisma with soft-delete and order status audit history across 8 interrelated services required careful relation and enum planning upfront. Adding Google OAuth after the core JWT auth system was already built meant retrofitting the User model to support nullable passwords, backfilling profile images for existing accounts without overwriting manually uploaded avatars, and getting the CORS/redirect configuration right across separate frontend (Vercel) and backend (Render) origins.