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
MRGVVercel
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.

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.
Decisions & deliverables
- Migration-roadmap document
- Serverless viability study
- Frontend and backend architecture diagrams
- SSO, session and authentication integration with Okta
- Components for authentication, session, events, authors and checkout
- Endpoints including /payment, /auth, /venues, /products and /orders
- Jest integration tests
- API and UI performance optimization
- Vercel-to-AWS integration diagram
- Lambda-types diagram
- Event-driven architecture diagram
- Network diagram
- serverless APIs
- event-driven integration
- VPC and network boundaries
- authentication and authorization
- payment and CRUD workflows
Technology
- ReactJS
- MongoDB
- TypeScript
- API Gateway
- AWS Lambda
- Amazon SNS
- Amazon SQS
- Mongoose ODM
- CloudFormation
- Terraform
- Next.js
- JavaScript
Evidence archive
Real diagrams, interfaces and documents.
Open any artifact to inspect the full local image.
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.






