← Back to all projects

05 · Cloud · Notion + Miro/PDF

Nextjs Api Migration to Serverless

Move a scaling backend from Vercel to AWS while introducing DDD/SOLID boundaries, observability and a security layer.

Project context — organizations, products, and platforms evidenced in the source

MRG logoMRG
VVercel
AAWS
AAdmitOne
OOkta
SSage
SSendGrid
SSquare
TTipalti
Role
Solutions Architect · Back-End · Front-End · Dev Ops
Domain
Cloud
Sources
Notion + Miro/PDF
Published artifacts
8
Evidence archiveOverall MRG AWS architecture.
Overall MRG AWS architecture.
Overall MRG AWS architecture.

Context

The problem and its boundary.

Migration and integration architecture spanning API Gateway, Lambda, VPC networking, event processing, authentication/authorization, payments and CRUD APIs.

The restored board is in Alexsandro's authenticated corpus and was last modified by him; the frames are dated September 2022.

No explicit in-frame role credit or production-result evidence was observed.

Decisions & deliverables

  1. Migration-roadmap document
  2. Serverless viability study
  3. Frontend and backend architecture diagrams
  4. SSO, session and authentication integration with Okta
  5. Components for authentication, session, events, authors and checkout
  6. Endpoints including /payment, /auth, /venues, /products and /orders
  7. Jest integration tests
  8. API and UI performance optimization
  9. Vercel-to-AWS integration diagram
  10. Lambda-types diagram
  11. Event-driven architecture diagram
  12. Network diagram
  13. serverless APIs
  14. event-driven integration
  15. VPC and network boundaries
  16. authentication and authorization
  17. payment and CRUD workflows

Technology

  • ReactJS
  • MongoDB
  • TypeScript
  • API Gateway
  • AWS Lambda
  • Amazon SNS
  • Amazon SQS
  • Mongoose ODM
  • CloudFormation
  • Terraform
  • Next.js
  • JavaScript

What this archive can prove

Published authorship. Claims proportional to the source.

  • No repository, public deployment link, before/after metrics, date or post-migration result is present.
  • The page does not separate completed implementation from roadmap/proposal scope.
  • The MRG cover is duplicated across another Notion case and should not be treated as unique evidence.