core
sst
Our great sponsors
core | sst | |
---|---|---|
18 | 179 | |
1,489 | 19,906 | |
1.9% | 2.3% | |
9.4 | 9.9 | |
9 days ago | 7 days ago | |
C | TypeScript | |
Apache License 2.0 | 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.
core
-
Show HN: Pip Imports in Deno
An alternative is metacall. The example in the readme is about calling Python from Javascript, but it also works with other languages, like Ruby, C#, Java, and other languages
https://github.com/metacall/core
List of supported languages here https://github.com/metacall/core/blob/develop/docs/README.md...
In the future, maybe webidl (or extensions of it) will bring interoperability between languages too. At the moment there is https://mozilla.github.io/uniffi-rs/ for interoperability between Rust and a number of languages (basically the ones mozilla needs: Swift, Kotlin, Javascript)
-
Python frontend with Zig backend
Hi, I am writing a Polyglot Runtime called MetaCall, it provides interoperability between many different languages: https://github.com/metacall/core
-
Gitpodify the MetaCall
In this blog, i will be automating the setup of metacall/core on Gitpod.
MetaCall helps you build serverless applications using a more fine-grained, scalable and NoOps oriented Function Mesh instead of ServiceMesh and DevOps approach. It automagically converts your code into a Function Mesh and auto-scales individual hot parts or functions of your app.
-
Ideas for Intermediate or Advanced Rust Projets?
We are building a Polyglot Runtime and we are adding support for Rust, if you are interested you can participate on it: https://github.com/metacall/core
-
Make & Deploy Doxygen
MetaCall Polyglot Runtime MetaCall.io | Install | Docs
-
Ask HN: Solo-preneurs, how do you DevOps to save time?
I try to avoid any complicated tool and simplify my life with NoOps tools. Using Kubernetes or AWS from scratch is probably going to kill your startup.
In my case, I have tried MetaCall: https://metacall.io
- Tell HN: Heroku bans 10 year account without notice or explanation
- Write libraries instead of services, where possible
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
-
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.
-
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).
-
Rethinking Serverless with Flame
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
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)
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.
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-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
esbuild - An extremely fast bundler for the web
docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
sst-start-demo - A simple SST app to demo the new `sst start` command
next-auth - Authentication for the Web.
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
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
goja - ECMAScript/JavaScript engine in pure Go