sst VS sst-start-demo

Compare sst vs sst-start-demo and see what are their differences.

sst-start-demo

A simple SST app to demo the new `sst start` command (by sst)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
sst sst-start-demo
179 14
19,641 18
3.1% -
9.9 0.0
8 days ago 7 months ago
TypeScript JavaScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of sst. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-20.
  • The 2024 Web Hosting Report
    37 projects | dev.to | 20 Feb 2024
    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
    6 projects | news.ycombinator.com | 9 Feb 2024
    > 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
    2 projects | dev.to | 6 Feb 2024
    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
    2 projects | dev.to | 5 Feb 2024
    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?
    7 projects | news.ycombinator.com | 23 Jan 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

  • Create a Next.js Server Component S3 Picture Uploader with SST
    5 projects | dev.to | 4 Jan 2024
    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.
  • Do you believe AI will replace your job?
    2 projects | dev.to | 14 Dec 2023
    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).
  • Rethinking Serverless with Flame
    5 projects | news.ycombinator.com | 6 Dec 2023
    I think the casing is not enforced by HN but rather up to the poster?

    > (Aside: I wish someone would rethink Serverless, heh.)

    Not sure if you've checked out https://sst.dev/ but I think they've done precisely that. For example, they have Live Lambda Development which makes local dev a real breeze by significantly shortening feedback loops (no need to push your code up to the cloud and wait for it to deploy)

  • A bank runs serverless with PHP and AWS Lambda
    2 projects | news.ycombinator.com | 1 Nov 2023
    What is "SST" in this context? Is it this thing? https://sst.dev/

    I'm having trouble understanding where PHP fits into this scenario. If your cloud backend is in PHP, can't you just host that anywhere, separate from your frontends? Where does the serverless come in? And which did you use? (There are so many out there now, from AWS Lambda to Cloudflare to Fastly, etc.)

    If you're not limited to AWS, Google's Cloud Run lets you containerize a PHP app and auto-scale it up and back down to zero in bursts, for example. It's not really serverless, just an auto-scaling VM that goes up and down as needed.

  • A Beginner's Guide to the Serverless Application Model (SAM)
    7 projects | dev.to | 16 Aug 2023
    Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

sst-start-demo

Posts with mentions or reviews of sst-start-demo. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-14.
  • Hosting Nextjs using Lamda functions
    4 projects | /r/nextjs | 14 Jun 2022
    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
    2 projects | /r/serverless | 12 Jun 2022
    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?
    2 projects | /r/webdev | 6 Jun 2022
    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?
  • A magical AWS serverless developer experience
    8 projects | news.ycombinator.com | 27 Mar 2022
    > 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
    3 projects | dev.to | 22 Mar 2022
  • SST: The Most Underrated Serverless Framework You Need to Discover (part 2)
    6 projects | dev.to | 13 Nov 2021
    documentation which is top notch
  • Serverless Framework vs SAM vs AWS CDK
    7 projects | dev.to | 7 May 2021
    The CDK CLI doesn't bring the same utility around testing and debugging as SAM and Serverless does but it is possible to use the SAM CLI together with the CDK to help bridge the gap. There's also a newcomer on the block, Serverless-Stack, an extension of the CDK, that brings a lot of testing utility and serverless specific constructs.
  • Design pattern for serverless large rest API
    2 projects | /r/aws | 25 Apr 2021
    Make sure you look into SLS Framework (https://www.serverless.com) or SST (https://docs.serverless-stack.com).
  • Work on your Lambda functions live
    2 projects | dev.to | 26 Jan 2021
    You can try out this sample repo here.

What are some alternatives?

When comparing sst and sst-start-demo you can also consider the following projects:

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-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

esbuild - An extremely fast bundler for the web

serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project

docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment

next-auth - Authentication for the Web.

prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.

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.

webiny-js - Open-source serverless enterprise CMS. Includes a headless CMS, page builder, form builder, and file manager. Easy to customize and expand. Deploys to AWS.

serverless-next.js - ⚡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components

serverless-application-model - The AWS Serverless Application Model (AWS SAM) transform is a AWS CloudFormation macro that transforms SAM templates into CloudFormation templates.