next-cache-effective-pages VS serverless-next.js

You can see that it misses the cache every time, and this is what I am trying to avoid (by using https://github.com/bmstefanski/next-cache-effective-pages) :D

Let's say you want to re-generate a static file (e.g. public/sitemap.xml) every 15 minutes. The first solution that comes to mind is doing this at build time and it's great and simple, but.... it wouldn't work for mid and big-scale applications (considering that you're rebuilding your app every time there's a change in CMS). And this is where the next-cache-effective-pages library comes into the picture.It makes it easier to change your static file into a regeneratable page without you worrying about effective caching and bandwidth attacks.

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 .