sst
apprunner-roadmap
sst | apprunner-roadmap | |
---|---|---|
179 | 62 | |
20,392 | 289 | |
3.3% | 1.0% | |
9.8 | 0.0 | |
3 days ago | about 3 years ago | |
TypeScript | ||
MIT License | GNU General Public License v3.0 or later |
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
-
The 2024 Web Hosting Report
We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!
-
Hono v4.0.0
> But if you have a sufficiently large enough API surface, doing one lambda per endpoint comes with a lot of pain as well. Packaging and deploying all of those artifacts can be very time consuming, especially if you have a naive approach that does a full rebuild/redeploy every time the pipeline runs.
Yeah, thankfully SST [0] does the heavy lifting for me. I've tried most of the solutions out there and SST was where I was the happiest. Right now I do 1 functions per endpoint. I structure my code like url paths mostly, 1 stack per final folder, so that the "users" folder maps to "/users/*" and inside I have get/getAll/create/update/delete files that map to GET X/id, GET X, POST X, POST X/id, DELETE/id. It works out well, it's easy to reason about, and deploys (a sizable a backend) in about 10min on GitHub Actions (which I'm going to swap out probably for something faster).
I agree with the secrets/permissions aspect and I like that it's stupid-simple for me to attach secrets/permissions at a low level if I want.
I use NodeJS and startup isn't horrible and once it's up the requests as very quick. For my needs, an the nature of the software I'm writing, lambda makes a ton of sense (mostly never used, but when it's used it's used heavily and needs to scale up high).
[0] https://sst.dev
-
Lambda to S3: Better Reliability in High-Volume Scenarios
We will start by building a project with SST that provisions an API Gateway, a Lambda, and an S3 bucket. Once implemented, we'll look into testing for concurrent write conflicts or exceeding capacity limits.
-
How I saved 90% by switching NATs
I recently deployed a node websocket server using the SST Service construct. Until this point my stack had been functions and buckets. While I had no users 😢, I also had no costs 🤡.
-
Ask HN: What web development stack do you prefer in 2024?
Most my personal and side-business projects have very spiky load or just low load in general. Because of that I love using AWS Lambda as my backend since it scales to 0 and scales to whatever you have your limits set at.
I use SST [0] for my backend with NodeJS (TypeScript) and Vue (Quasar) for my frontend. For my database I use either Postgres or DynamoDB if the fit is right (Single Table Design is really neat). For Postgres I like Neon [1] though their recent pricing changes make it less appealing.
[0] https://sst.dev
[1] https://neon.tech
-
Meta's serverless platform processing trillions of function calls a day (2023)
Yup. Entire core business product for a succeeding startup, though it's a small team of contributors (<10), and a much smaller platform team. Serverless backend started in 2018. Been a blessing in many regards, but it has its warts (often related to how new this architecture is, and of course we've made our own mistakes along the way).
I really like the model of functions decoupled through events. Big fan of that. It's very flexible and iterative. Keep that as your focus and it's great. Be careful of duplicating config, look for ways to compose/reuse (duh, but definitely a lesson learnt) and same with CI, structure your project so it can use something off-the-shelf like serverless-compose. Definitely monorepo/monolith it, I'd be losing my mind with 100-150 repos/"microservices" with a team this size. If starting now I'd maybe look at SST framework[0] because redeploying every change during development gets old fast
I couldn't go back to any other way to be honest, for cloud-heavy backends at least. By far the most productive I've ever been
Definitely has its warts though, it's not all roses.
[0] http://sst.dev
-
Building a sophisticated CodePipeline with AWS CDK in a Monorepo Setup
Along the way, you find an excellent framework, SST. Which is much faster than CDK and provides a better DX1. Here is how you then define your MultiPipelineStack.
-
Create a Next.js Server Component S3 Picture Uploader with SST
SST is a powerful framework that simplifies the development of serverless applications. It offers a straightforward and opinionated approach to defining serverless apps using TypeScript. Built on top of AWS CDK, SST handles the complexity of setting up your serverless infrastructure automatically. SST is an open-source framework and is completely free to use.
- SST – modern full-stack applications on AWS
-
Do you believe AI will replace your job?
SST is an open-source framework designed to facilitate the development and deployment of Serverless stacks on AWS. It operates under the hood by integrating with Amazon CDK. However, its primary benefit is in allowing us to concentrate on creating resources using familiar languages like TypeScript, treating them as Infrastructure as Code (IaC).
apprunner-roadmap
- AWS AppRunner doesn't support WebSockets
-
The 2024 Web Hosting Report
Examples for products in this category are: Google Cloud Run, AWS App Runner, Azure Container Apps. Each has different scalability, cost, and integration trade-offs.
- AWS App Runner access logs
-
Rant: does anyone use AWS App Runner in production?
The deployment failed, and there were no logs available to help me debug the issue. There's an open issue on GitHub that has been around for over a year, but there doesn't seem to be a solution in sight.
-
Best Practices in AWS - ELB + Ingress?
If you're looking for something simple, that you can onboard to relatively quickly, that doesn't require a lot of oversight, consider App Runner, https://aws.amazon.com/apprunner/. EKS and Kubernetes are extremely powerful and flexible, but they come a fair amount of complexity. If you don't care about the orchestrator (or running your application in another cloud), try App Runner.
-
Security on AWS - AWS WAF x AWS App Runner
The reader will learn how to create a web application firewall with AWS WAF and AWS App Runner as a web application. AWS App Runner is an AWS service that deploys web applications or API using Amazon ECR or GitHub only. While AWS WAF (Web Application Firewall) is an AWS service that can protect the web application.
-
Getting started with ECS can be overwhelming. It involves working with multiple services and concepts like ECR, Fargate, Task Definitions, Clusters etc. Let's see a step by step tutorial which touches upon these concepts, builds a simple task and gets it deployed on ECS.
Yes, exactly. That's the problem. I found the issue here.
-
Be careful what you test or deploy to Vercel
I wonder what the aversion is to using a plain old server / vps. It's really not that difficult to deploy nowadays [0][1][2][3] and I'd rather get an $8 bill every month as insurance than ever worry about shit like OP just went through. It'll probably be more performant anyway due to cold starts and "edge" still having to hit us-east-1 for data.. cache your static files with Cloud Flare/Front. People are always surprised by how much traffic a single VPS can take[4] and believe it all has to be serverless to be web scale. I believe HN still runs on a single core or something.
There's a ton of places to get cloud credits as well, too many to link, so just Bing™ it
[0] https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_...
[1] https://aws.amazon.com/apprunner/
[2] https://cloud.google.com/run
[3] https://render.com/
[4] https://news.ycombinator.com/item?id=34676186
-
Does aws offer something like this?
AWS AppRunner could do more or less everything. You'd have to build a container image yourself, since AppRunner does not have C++ support for the "Code-based" service, but building a container really isn't more complex than installing that bare metal server. (Really, pick an OS, install dependencies, copy your code, start a service. That is all.)
-
How CodeCatalyst compares to other AWS Services related to Development and CI/CD processes
App Runner
What are some alternatives?
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
vite - Next generation frontend tooling. It's fast!
aws-app-runner - Repository for the blog post "Deploying a globally distributed API with AWS App Runner and Fauna"
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
Express - Fast, unopinionated, minimalist web framework for node.
esbuild - An extremely fast bundler for the web
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment
sst-start-demo - A simple SST app to demo the new `sst start` command
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
faunadb-js - Javascript driver for Fauna v4