sst VS sst-start-demo

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!

> 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

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.

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 🤡.

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

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

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.

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 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).

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.

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.

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?

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

I highly recommend serverless SST. https://docs.serverless-stack.com/

> 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???

documentation which is top notch

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

ServerlessStack framework