marko VS serverless-next.js

SolidJS and Tauri form another potent combination for creating performant, lightweight, and secure experiences. SolidJS is a reactive UI library that is similar to Svelte in the way it compiles away reactivity and updates the DOM directly, but it also incorporates a fine-grained reactivity system reminiscent of libraries like Marko, Knockout, and MobX.

Marko is a huge leap in the right direction. It has streaming, partial hydration, a compiler that optimizes your output, and a small runtime. I’ve also heard through the grapevine that Marko V6 also adds resumability to the framework as well.

Nevertheless, the future of JS frameworks is exciting. As we’ve seen from the data, Astro is doing some things right alongside Qwik. However, more noteworthy frameworks such as Marko and Solid are also paving the path forward with some similar traits and better performance benchmarks. We’ve come back full circle in web development - from PHP/Rails to SPAs and now back to SSR. Maybe we just need to break the cycle.

If you want more, take a look on Marko, fresh, qwik or pug. Dind't tested yet but they look like same as Nunjucks.

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 .