serverless-next.js VS sveltekit-adapter-lambda

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 .

I have a sveltekit app, it talks to an AWS REST backend so I would prefer to host it on AWS. I am exploring different ways of doing this. I am thinking of deploying to either Beanstalk or to Lambda or Serverless. I have played with Pulumi which looks pretty nice, but I could not get AWS to read the artefact zip file correctly after following all the instructions. Could not find package.json but it was there. Yes I zipped the files not the folder. I also tried sveltekit-adapter-lambda which uses serverless, but I hit problems with none of the static assets being accessible. Sites up, but 404s on all the js and css. They are there on the S3 bucket and being served up ok via the bucker URL but not coming through the lambda function.

Please take a look at this https://github.com/yarbsemaj/sveltekit-adapter-lambda