serverless-next.js VS aws-sam-typescript-layers-example

I'm currently waiting SST v2 to be released where they will use https://open-next.js.org instead of https://github.com/serverless-nextjs/serverless-next.js

To deploy the app, I had the requirement to use AWS as a cloud-provider, with a limited budget, so neither Vercel (a safe choice, as it is the company which develops Next.js), nor a containerized solution like the managed AWS ECS Fargate service could satisfy my needs. Then, I started with a serverless hosting thanks to the serverless-next project, which provides a serverless plugin or a CDK construct to deploy a Next.js stack. However, this project is no more well-maintained and new Next.js features (like middlewares, etc.) are not supported.

If you have the time and resources, I'd suggest to take a look at SST.dev and or OpenNext (created by the SST people). With that ISR should work (although they still seem to work on upgrading to v12). Or take a look at https://github.com/sladg/nextjs-lambda to run NextJS on a lambda exclusively.

serverlessnextjs does not support NextJS 13. https://github.com/serverless-nextjs/serverless-next.js/issues/2497

I hate Amplify. I've been using it for around 2 weeks, because serverless-next.js no longer works with Next v13.

Let's mention that it's possible to deploy a Next.js application using SST 😅. This setup relies on the serverless-next.js project and it's hidden behind a construct named NextJsSite. It can be a very efficient solution when you want to ship your application on AWS environment (I use it for a production workload in my current company).

ATM Next JS is SSR (Server Side Rendering) so only S3 and CloudFront is not enough! As mentioned here already Lambda@Edge can do the server parts and is used like in Amplify. An Alternative would the serverless framework which offers a next js deployment https://github.com/serverless-nextjs/serverless-next.js .

Inspired by this blogpost, I've hacked together a small AWS Serverless application powered by SAM, which calculates your work remote savings. I hope find this fun!

Recently, I've been working on this project where we are using SAM with Typescript. Long story short, AWS SAM does not support TypeScript out of the box. So I had to create a makefile in order to build each lambda function. More details on this implementation here.

I will say, I've since moved past this a little bit, although not entirely. I still have the Lambda code, but I can build and run locally (it took me a while to figure out how to run an AWS web server locally). And, I found a tutorial that uses Typescript and Makefiles with AWS Lambdas. Not entirely sure I want to buy into their model, but it's something and continues to allow a clean CI/CD environment. That's my biggest concern and why I asked the original question.