How moving to serverless Nuxt sped up our time to market
summary
Migrating an Angular site to Nuxt on a serverless stack speeds delivery by removing server provisioning and shrinking front-end artifacts. The setup uses S3 + CloudFront + Route53 for hosting and API Gateway + Lambda + DynamoDB for the backend, with TypeScript and Axios. The team builds a GPS/trip verification dashboard and gets a full front-end done in ~60 hours when the backend is already known. Challenges: secrets get baked into static manifests so secrets move behind APIs, and SAML/OIDC required a middleware SAML callback workaround while an OpenID PR awaits.
AI-written summary · about
chapters (8)
- 0:00Introduction to serverless
- 1:28Defining serverless
- 2:18Serverless architecture
- 4:53Transition to Nuxt
- 7:31Nuxt features and modules
- 10:24Project implementation
- 12:17Overcoming challenges
- 15:06Future goals and conclusion
related talks
23mFell Static with Nuxt
23mFull Stack Vue in the Era of Serverless Computing
33mGoing Serverless with VueJS
31mAccelerate business innovation with serverless applications
51mServerless - a backend thing that gives superpowers to frontend developers
44mServerless: Giving superpowers to frontend developers
54mServerless Architectures: no servers allowed!
24mServerless functions and Vue.js
