sst

Build full-stack apps on your own infrastructure. (by sst)

Sst Alternatives

Similar projects and alternatives to sst

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better sst alternative or higher similarity.

sst discussion

Log in or Post with

sst reviews and mentions

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-11-04.
  • We're Leaving Kubernetes
    14 projects | news.ycombinator.com | 4 Nov 2024
    wow very very interesting. I think we can discuss about it on hours.

    1.) What would you think of things like hetzner / linode / digitalocean (if stable work exists)

    2.) What do you think of https://sst.dev/ or https://encore.dev/ ? (They support rather easier migration)

    3.) Could you please indicate the split of that 1 million $ in devops time and google cloud costs unnecessarily & were there some outliers (like oh our intern didn't add this specific variable and this misconfigured cloud and wasted 10k on gcloud oops! or was it , that bandwidth causes this much more in gcloud (I don't think latter to be the case though))

    Looking forward to chatting with you!

  • How to deploy a Next.js app to a Hetzner VPS using SST and Docker
    3 projects | dev.to | 12 Aug 2024
    SST is a framework that makes it easy to build modern full-stack applications on your own infrastructure. SST v3 uses Pulumi and Terraform – SST Documenation
  • Why are people paying so much for Vercel?
    1 project | news.ycombinator.com | 22 Jul 2024
    SST[1] looks pretty cool. Does it replicate the entire infrastructure Vercel attempts to provide you regarding hosting (such as CDN, caching, etc)?

    [1]. https://sst.dev/

  • Vercel ends open-source sponsorship program giving projects 24hr notice
    2 projects | news.ycombinator.com | 14 Jun 2024
    In case it’s helpful to anyone who has to jump off vercel:

    I recently had to transition my company off of vercel for reasons unrelated to this (wanted to use cloud infra primitives that vercel does not provide, and wanted to leverage the large amount of AWS credits my company received) and found that sst.dev [0] to be easy to migrate to and a joy to use in general. It leverages open-next to deploy next.js projects on AWS in a serverless way.

    I’ve been enjoying using it so much that for my next project I think I’ll skip vercel altogether and use sst from the start.

    [0] https://sst.dev/

  • 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

  • Meta's serverless platform processing trillions of function calls a day (2023)
    1 project | news.ycombinator.com | 17 Jan 2024
    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

  • A note from our sponsor - SaaSHub
    www.saashub.com | 4 Nov 2024
    SaaSHub helps you find the best software and product alternatives Learn more β†’

Stats

Basic sst repo stats
183
21,726
9.3
4 days ago

sst/sst is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of sst is TypeScript.


Sponsored
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai