You could link to faasta.xyz in github about and add EXAMPLES there.
The lambdas should be able to be accessible via http(s) e.g.
https://square.faasta.xyz/3 => 9
https://faasta.xyz/square/3 => 9
Great idea if done right!
Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
11–20 of 33 posts
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#12Since there is no LICENSE in the repo, I assume this will not be an open source project? Will it have an open core or similar license?
The plan is for it to be an opensource project, currently the cli and interface crates are MIT, I have been considering a copyleft license for the server, or a dual licensing strategy.
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#13You could link to faasta.xyz in github about and add EXAMPLES there. The lambdas should be able to be accessible via http(s) e.g. https://square.faasta.xyz/3 => 9 https://faasta.xyz/square/3 => 9 Great idea if done right!
Thanks for the feedback, I've added the URL to about,
I originally supported path prefix and subdomains, but I found it slightly more confusing to communicate to users. I'm definitely planning on more example.
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#14Bun likely has a larger footprint than this but it's also gaining lots of traction: https://bun.sh/docs/runtime/loaders
How might this project differentiate itself from Bun as it grows? Because Bun aims to be compact and fast (fast being the priority in their case).
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#15[flagged]
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#16Earlier quoted context omitted.
> After delving into this, it seems Wasmer tried, but as they weren't standards compliant, adoption/ecosystem support never followed. You may be surprised by how much WASIX is being adopted by the ecosystem! Aiming it to be full POSIX compliant has proven incredibly powerful, as there's no need for waiting for other entities to reinvent what already works in the POSIX (macOS, Linux, ...) :)
I'm not discounting WASIX or what you guys are doing I'd love to just use wasm today for everything instead of waiting, I started this project by trying to use WASIX, I just found it quite difficult to actually develop for as many of the essential rust crates, seemed reluctant to merge your changes, and having to use dependency versions from a year ago with patches is very frustrating.
Fair! We have already plans to solve the patching issue you commented... stay tuned!
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#17[flagged]
A more descriptive word would been self-hostable function as a service, that's why faas is in the name!
The point of serverless is you don't have to think about hosting, and ideally it's cheaper.
The problem is if the hosting provider goes away you're screwed. In the case of Faasta, it's a single static binary with minimal configuration so if that happens, you can host it your self or move to another provider.
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#18[flagged]
A more descriptive word would been self-hostable function as a service, that's why faas is in the name! The point of serverless is you don't have to think about hosting, and ideally it's cheaper. The problem is if the hosting provider goes away you're screwed. In the case of Faasta, it's a single static binary with minimal configuration so if that happens, you can host it your self or move to another provider.
How can you "not have to think about hosting" while self-hosting?
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#19Unfortunate name collision with FASTA the bioinformatic sequence file format
Re: Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust
#20Earlier quoted context omitted.
A more descriptive word would been self-hostable function as a service, that's why faas is in the name! The point of serverless is you don't have to think about hosting, and ideally it's cheaper. The problem is if the hosting provider goes away you're screwed. In the case of Faasta, it's a single static binary with minimal configuration so if that happens, you can host it your self or move to another provider.
How can you "not have to think about hosting" while self-hosting?
Well at that point you'll obviously start having to think about it. The point is you can easily move to self-hosting without rewriting everything.