sst-start-demo
terraform-aws-next-js
Our great sponsors
sst-start-demo | terraform-aws-next-js | |
---|---|---|
14 | 9 | |
18 | 1,433 | |
- | 0.9% | |
0.0 | 0.0 | |
8 months ago | 4 months ago | |
JavaScript | TypeScript | |
MIT License | Apache License 2.0 |
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.
sst-start-demo
-
Hosting Nextjs using Lamda functions
https://docs.serverless-stack.com and https://www.serverless.com/ can support next. However serverless-stack is too new and serverless framework looks promising but it uses an old version of serverless plugin.
-
Serverless backend with or without a backend framework
I'm new to serverless and I've recently discovered frameworks like the Serverless Framework and SST. I've seen examples of Lambda functions where people interact with DBs like DynamoDB, authenticating users with Cognito and using API Gateway to map routes (these are all AWS-specific terms), which seems to me like you can pretty much build a CRUD API on top of this. However, I've also seen examples like this one where you can deploy a backend framework such as Nest.js as a single lambda function.
-
Has anyone tried combining serverless functions with Nest.js?
Hey all, recently I've been learning a lot about serverless APIs and I discovered frameworks like Serverless and SST which look great. I then also discovered that you can apparently deploy a Nest.js backend as a lambda handler -- here is a relevant article. Has anyone tried this? If you are looking to start working on a new project, is it a good idea to combine these together, or would you be better off just writing individual lambda handlers without a framework like Nest?
-
Deploying a Nextjs
Hosting NextJS apps on AWS I would recommend https://docs.serverless-stack.com/ which has an inbuilt CDK pre-configured NextJS setup or https://registry.terraform.io/modules/dealmore/next-js/aws/latest
-
Why I should use a backend when I can use AWS Amplify,App-Sync and Cognito
I highly recommend serverless SST. https://docs.serverless-stack.com/
-
A magical AWS serverless developer experience
> The ability to move between the frontend, backend, and infrastructure code without having to learn a different language is invaluable to every member of the team.
I'm actually quite skeptical of this claim. Learning a new language isn't really a big deal unless you are using relatively "esoteric" stuff like clojure or elixir which really require an experienced consultant to train your team.
With AWS Chalice, we've been able to ship production scale code (for govcloud) in Python without any one of us breaking the environment by simply using separate staging. We were able to get PHP/Javascript developers to use it with barely any downtime. In fact it was more or less appreciated from the clean and simple nature of Python right from the get go.
This feels like way too much engineering from the get go. Here's my workflow with AWS Chalice and its super basic (I'm open to improvements here).
- checkout code from github
- run localhost and test endpoints written in python (exactly like Flask)
- push to development stage API gateway
- verify it is working as intended and this is when we catch missing IAM roles, we document them. if something is wrong with our AWS setup (we dont use CDK just simply use the AWS console to set everything up once like VPC and RDS)
- push to production stage API gateway
All this shimming, typescript (rule of thumb is ~40% more code for 20% improvement through less documentation and type errors, only really valid in large teams) separate AWS developer accounts seems overkill.
The one benefit I see from all this extra compartmentalization is if you are working in large teams for a large company since you are going to discover missing IAM roles and permissions anyways and is part of being an implicit "human AWS compiler trying different stackoverflow answers".
Some positives I see are CDK but if you are deploying your infrastructure once, I really don't see the need for it, unless you have many infrastructures that can benefit from boilerplate generation.
Happy to hear from all ends of the spectrum, serverless-stack could be something I explore this weekend but there's just so much going on and I'm getting lot of marketing department vibes from reading the website (like idea to ipo and typescript for all) and to top it off
going to https://docs.serverless-stack.com/ triggers an antivirus warning about some netlify url ( nostalgic-brahmgupta09582d1.netlify.app) what is going on here???
- My Favorite Infrastructure as Code (IAC) Tool
-
SST: The Most Underrated Serverless Framework You Need to Discover (part 2)
documentation which is top notch
-
Easy practical guide to serverless framework with AWS
On a related note, shout out to https://docs.serverless-stack.com/ which is kinda like Serverless Framework except build on the CDK. Much more solid IMHO
-
Debugging Serverless API Issues
ServerlessStack framework
terraform-aws-next-js
-
Vite vs NextJS for Dashboard App
source: https://github.com/milliHQ/terraform-aws-next-js/tree/v0.x
-
Hosting Nextjs using Lamda functions
I found terraform modules, but these seem dated https://github.com/milliHQ/terraform-aws-next-js
-
NextJS on AWS with vs. without Serverless framework
On a non-Amplify note, are you by any chance familiar with how terraform-aws-next-js sets up the lambda function?
-
I'm not using Vercel and it's killing me
It currently has a few limitations on ISG and using Middleware, but otherwise supports a wide range of features: https://github.com/milliHQ/terraform-aws-next-js
-
What features do I miss out on if I host with AWS instead of Vercel?
So if youโre using AWS, I highly recommend checking this out https://github.com/milliHQ/terraform-aws-next-js
- Cheaper Vercel alternatives specifically to deploy Next.js apps?
-
Anyone hosting a nextjs app in AWS?
AWS https://github.com/dealmore/terraform-aws-next-jsWhich is as close to Vercel as your going to get on AWS; We have not been using this particular library ourselves yet, we built our own setup. But this setup is alot better than our one.
- Deploy Next.js App on AWS (EC2, EB and Lambda)
-
Why we self-host our serverless Next.js site on AWS with Terraform
We open sourced the module on GitHub: https://github.com/dealmore/terraform-aws-next-js
What are some alternatives?
sst - Build modern full-stack applications on AWS
serverless-next.js - โก Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
nextjs-azure-function - Builds your NextJS Api folder into a single azure function.
serverless-application-model - The AWS Serverless Application Model (AWS SAM) transform is a AWS CloudFormation macro that transforms SAM templates into CloudFormation templates.
chrome-aws-lambda - Chromium Binary for AWS Lambda and Google Cloud Functions
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
Quick Start - ๐ A Node.js Serverless Framework for front-end/full-stack developers. Build the application for next decade. Works on AWS, Alibaba Cloud, Tencent Cloud and traditional VM/Container. Super easy integrate with React and Vue. ๐
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.
sls-vs-sam-vs-cdk - SLS vs SAM vs CDK