lift
serverless-next.js
lift | serverless-next.js | |
---|---|---|
5 | 35 | |
904 | 4,391 | |
0.8% | 0.3% | |
4.7 | 0.0 | |
8 days ago | 7 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lift
-
Send emails asynchronously with Sendgrid and node.js, AWS SQS, AWS Lambda
The template utilizes the lift plugin to leverage AWS CDK and expand Serverless' functions to avoid all the yak-shaving at the beginning. One can always tweak the parameters afterward, be it from the serverless.yml configuration file or directly from the AWS console.
-
Serverless can benefit from not being so Lambda-centric
Such implementation opens up a lot of new possibilities: a functionless RESTful API where the only code is configuration-only IaC is not out of reach anymore and can help team achieve cheaper, more robust code base with minimal efforts. Such implementation is currently under discussion within Lift project where your feedbacks on the implementation are highly valued.
-
Lift 1.9: support for FIFO queues (Lift integrates CDK in serverless.yml)
Not yet, we're considering this: https://github.com/getlift/lift/pull/52 Any feedback on this is appreciated, ideally in the pull request -> we use that to measure interest. We try to judge which features to implement based on community feedback.
- Lift 1.0: AWS CDK constructs in the Serverless Framework
serverless-next.js
-
My SaaS architecture (tech stack) on AWS as a solo developer with Node.js as a backend
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
-
Deploying Next.js 13 with Amplify CDK
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.
-
Have you noticed that AWS Amplify and NextJS don't seem to get as much attention as they deserve?
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.
-
Are there disadvantages to running NextJS on Lambda with Serverless framework?
serverlessnextjs does not support NextJS 13. https://github.com/serverless-nextjs/serverless-next.js/issues/2497
-
I hate Amplify
I hate Amplify. I've been using it for around 2 weeks, because serverless-next.js no longer works with Next v13.
-
π Next Auth vs SST Auth
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).
- Next.js com serverless-stack
- Is Turbopack 10x Faster than Vite?
- Astro 1.0
-
What are some good ways to deploy a react app on AWS?
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 .
What are some alternatives?
serverless - This is intended to be a repo containing all of the official AWS Serverless architecture patterns built with CDK for developers to use. All patterns come in Typescript and Python with the exported CloudFormation also included.
terraform-aws-next-js - Terraform module for building and deploying Next.js apps to AWS. Supports SSR (Lambda), Static (S3) and API (Lambda) pages.
sst - Build modern full-stack applications on AWS
nextjs-monorepo-example - Collection of monorepo tips & tricks
serverless-iam-roles-per-function - Serverless Plugin for easily defining IAM roles per function via the use of iamRoleStatements at the function level.
aws-sam-typescript-layers-example - Example project for developing AWS Lambda functions on TypeScript with all goodies: local development, tests, debugging, shared layers (3rd party and your own), and deploy.
serverless-ide-vscode - Serverless IDE: Enhanced support for AWS SAM and CloudFormation in VS Code
nextjs-ssr-cdk-aws - π¦ βββ ββββ ββββ βNext.js webapp using Server Side Rendering (SSR) and Incremental Static Regeneration (ISR) deployed with Serverless Nextjs CDK construct on AWS using CloudFront and Lambda@Edge [Moved to: https://github.com/ibrahimcesar/nextjs-ssr-isr-cdk-aws]
aws-swaggerui - Serverless Swagger UI for API Gateway
sveltekit-adapter-lambda - An adapter to build a SvelteKit app into a lambda ready for deployment with lambda proxy via the Serverless Framework.
clickstream-analytics-on-aws - Build clickstream analytics on AWS for your mobile and web applications