Our great sponsors
|26 days ago||19 days ago|
|Apache License 2.0||Apache License 2.0|
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.
2 projects | dev.to | 13 Aug 2022
Show HN: Distributed SQLite on FoundationDB
5 projects | news.ycombinator.com | 28 Jul 2022
Hello HN! I'm building mvsqlite, a distributed variant of SQLite with MVCC transactions, that runs on FoundationDB. It is a drop-in replacement that just needs an `LD_PRELOAD` for existing applications using SQLite.
I made this because [Blueboat](https://github.com/losfair/blueboat) needs a native SQL interface to persistent data. Apparently, just providing a transactional key-value store isn’t enough - it is more easy and efficient to build complex business logic on an SQL database, and it seems necessary to bring a self-hostable distributed SQL DB onto the platform. Since FoundationDB is Blueboat’s only stateful external dependency, I decided to build the SQL capabilities on top of it.
At its core, mvsqlite’s storage engine, mvstore, is a multi-version page store built on FoundationDB. It addresses the duration and size limits (5 secs, 10 MB) of FDB transactions, by handling multi-versioning itself. Pages are fully versioned, so they are always snapshot-readable in the future. An SQLite transaction fetches the read version during `BEGIN TRANSACTION`, and this version is used as the per-page range scan upper bound in future page read requests.
For writes, pages are first written to a content-addressed store keyed by the page's hash. At commit, hashes of each written page in the SQLite transaction is written to the page index in a single FDB transaction to preserve atomicity. With 8K pages and ~60B per key-value entry in the page index, each SQLite transaction can be as large as 1.3 GB (compared to FDB's native txn size limit of 10 MB).
mvsqlite is not yet "production-ready", since it hasn’t received enough testing, and I may still have a few changes to make to the on-disk format. But please ask here if you have any questions!
2 projects | news.ycombinator.com | 26 Jul 2022
This sounds quite a bit like Cloudflare Workers, and they have a comparison page - https://github.com/losfair/blueboat/wiki/Comparison-with-Clo....
Are V8 isolates the future of computing?
Blueboat may be what you’re looking for
> If one writes Go or Rust, there are much better ways to run them than targeting WASM
wasm has its place, especially for contained workloads that can be wrapped in its strict capability boundaries (think, file-encoding jobs that shouldn't access anything else but said files: https://news.ycombinator.com/item?id=29112713).
> Containers are still the defacto standard.
wasmedge , atmo , krustlet , blueboat  and numerous other projects are turning up the heat !
Blueboat, an open-source alternative to Cloudflare Workers
2 projects | news.ycombinator.com | 23 Nov 2021
Deno Deploy Beta 2
9 projects | news.ycombinator.com | 1 Sep 2021
They're not perfectly isolated to a high security standard such that you could deploy your own v8 workers SaaS. And they do have quirks and development woes. I haven't tested in production but if it's just your trusted apps wanting to exceed the cloudflare workers 30 scripts limit then both are wonderfully powerful solutions to put behind a https proxy.
- Are V8 isolates the future of computing?
Netlify Edge Functions: A new serverless runtime powered by Deno
6 projects | news.ycombinator.com | 19 Apr 2022
Edge functions are typically run intermittently, with their runtime stopped to free up resources between runs. Therefore a big factor is startup and shutdown speed. Containers are pretty bad there. Deno is better, and WASM is unbeatable, especially with things like Wizer.
Building a WebAssembly-powered serverless platform
4 projects | reddit.com/r/programming | 18 Apr 2022
I imagine startup cost could be amortized by something like wizer: https://github.com/bytecodealliance/wizer
Is it possible in Rust to save the complete state of a program and restore it later? Such as may be accomplished in some implementations of Common Lisp
2 projects | reddit.com/r/rust | 20 Feb 2022
See https://github.com/bytecodealliance/wizer for an implementation of this approach.
8 projects | news.ycombinator.com | 2 Jun 2021
Besides that I think Wizer  is both an elegant and a simple solution to speed up startup speed with Wasm.
 - https://github.com/bytecodealliance/wizer#using-wizer-as-a-l...
A similar project, for WebAssembly so with limited scope is this: https://github.com/bytecodealliance/wizer. And somehow similar but limited on LLVM IR a colleague worked on this for Cheerp (the compiler used here as backend): https://github.com/leaningtech/cheerp-meta/wiki/Cheerp-PreExecuter.
What are some alternatives?
wasmtime - A fast and secure runtime for WebAssembly
TablaM - The practical relational programing language for data-oriented applications
go - The Go programming language
go-wasm-bake - Experimenting with eager evaluation of Go WASM code
deploy_feedback - For reporting issues with Deno Deploy
jose - "JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS for Node.js, Browser, Cloudflare Workers, Deno, Bun, and other Web-interoperable runtimes.
wasmer - 🚀 The leading WebAssembly Runtime supporting WASI and Emscripten
wagi - Write HTTP handlers in WebAssembly with a minimal amount of work
component-model - Repository for design and specification of the Component Model