sst-start-demo
Previous Serverless Version 0.5.x
Our great sponsors
sst-start-demo | Previous Serverless Version 0.5.x | |
---|---|---|
14 | 90 | |
18 | 46,080 | |
- | 0.4% | |
0.0 | 8.2 | |
8 months ago | 2 days ago | |
JavaScript | JavaScript | |
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.
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
Previous Serverless Version 0.5.x
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Github | Website
-
Invocation error - can't find any results helping me to solve this issue
i deployed a lambda and http api gateway using a serverless.com (sls) template as a start. I get the following error when it processes a specific request:
- Consulta: buenas practicas AWS
-
Deploying Lambdas from Zipped Code on S3 vs Image Repository
Have you tried serverless.com ? It lets you have infrastructure as code.
-
[p] I built an open source platform to deploy computationally intensive Python functions as serverless jobs, with no timeouts
- With Lambda, you manage creating and building the container yourself, as well as updating the Lambda function code. There are tools out there such as sst or serverless.com which help streamline this.
-
AWS Lambda, a good host for a rest API?
If you'd like to use Lambda, usually you need to engineer FOR it, from day one, you don't (often) get to choose some other framework and shoehorn it into Lambda and Serverless. There's some great frameworks to help deploy code into Lambda easily and create REST endpoints for things, one such frameworks is serverless.com that helps easily deploy to it, but it lacks a framework for doing REST that also supports local emulation (as easily). For that, I recommend a framework by AWS called Chalice. This is an amazing REST framework that runs a proxy that works locally and deploys exactly the same on Lambda, it is Python however.
-
How are you deploying cloud functions (GCF/Lambda/Firebase/whatever) from your monorepos?
I use serverless.com for AWS stuff.
- First time building microservice-based application
-
Key learnings after 10h diving into Lambda, js and Github Actions
After knocking out a README with a set of goals and a list of TODOs to check off as I made progress, I spent about 10 hours over a weekend trying to get something to work. I used serverless for making Lambda easier, Github Actions for the deploy pipeline and store my credentials; and sadly I rolled my own access_token refresh logic because I couldn't find a helper that just did that for me! wtf!?
-
Does anyone use serverless framework with Workers?
Does everyone who uses Workers just use wrangler cli and the cloudflare console UI for everything or is anyone using other tools like serverless framework (https://serverless.com) instead? Looks like they added some support for cloudflare but haven't tried it yet.
What are some alternatives?
sst - Build modern full-stack applications on AWS
Zappa - Serverless Python
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.
apex
serverless-application-model - The AWS Serverless Application Model (AWS SAM) transform is a AWS CloudFormation macro that transforms SAM templates into CloudFormation templates.
python-lambda - A toolkit for developing and deploying serverless Python code in AWS Lambda.
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
drover - Drover is a command-line utility for deploying Python packages to Lambda functions.
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.
formidable - The most used, flexible, fast and streaming parser for multipart form data. Supports uploading to serverless environments, AWS S3, Azure, GCP or the filesystem. Used in production.
sls-vs-sam-vs-cdk - SLS vs SAM vs CDK
atlantis - Terraform Pull Request Automation