workers-wasi
SQLite
workers-wasi | SQLite | |
---|---|---|
5 | 40 | |
119 | 5,537 | |
0.0% | - | |
0.0 | 0.0 | |
about 1 year ago | 2 days ago | |
C++ | C | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
workers-wasi
-
WASM by Example
The examples seemed clear enough to read (I did not test them), but I felt than even when teaching by example there needs to be more overview and explanation. I.e., I would prefer an overview of WASM structure and use with examples, rather than just the examples. (I have some (but limited) experience using WASM.)
As for the utility of wasm, note also that Cloudflare workers can run WASM on edge servers [1], and that the Swift community has some support for compiling to wasm [2].
I've never really understood how wasm could do better than java bytecode, but I've been impressed with how much people are using lua and BPF. More generally, in a world of federated programming, we need languages client can submit that providers can run safely, without obviously leaking any secret sauce -- perhaps e.g., for model refinement or augmented lookup.
[1] https://github.com/cloudflare/workers-wasi
-
SQLite builds for WASI since 3.41.0
Those are great questions! I believe Emscripten will be required for some cases as it provides more features for targeting a Web Browser. If WASI is the only requirement for a Wasm module, then there are three possible solutions:
- Use a library that provides the WASI bindings in a browser environments: there are some OSS projects that provides WASI bindings on top of browser technologies. For example, workers-wasi from Cloudflare [1]. It could be even another Wasm module that provides the implementation for the main one. I know the people from Loophole Labs are experimenting with virtual filesystems (VFS) [2].
- Browsers provides a WASI implementation: server-oriented runtimes like NodeJS are already providing these bindings (under a experimental flag). I shouldn't have stated that as a fact, as browsers may provide it or not. However, I saw in the past the Google Chrome team experimenting with WASI and the browser FileSystem API [3]. So, I think it may happen :)
- [1] https://github.com/cloudflare/workers-wasi
- [2] https://www.youtube.com/watch?v=46jZSXVxYPw
- [3] https://github.com/GoogleChromeLabs/wasi-fs-access
-
The Tug-of-War over Server-Side WebAssembly
Indeed, some people are doing this:
- WASI once had an official polyfill https://wasi.dev/polyfill/, now apparently succeeded by https://github.com/bjorn3/browser_wasi_shim
- wasmer-js provides a JS polyfill for WASI https://docs.wasmer.io/integrations/js/wasi
- Cloudflare has a WIP polyfill https://github.com/cloudflare/workers-wasi
I'm generally leery of non-temporary polyfills, so I'm not sure that any of these feel like a long-term viable option for me.
-
Rust advocacy at a medium-sized startup
I think modern C++ could be perfectly viable as well. Maybe https://github.com/cloudflare/workers-wasi would be a good starting point? I'm not too knowledgeable on the subject. Exciting times though, I think WASM might be the great equalizer.
-
Store SQLite in Cloudflare Durable Objects
While there is a WASI implementation for Workers: cloudflare/workers-wasi, I prefer to implement each import manually - especially when there are so few and especially while I am still experimenting. This helps me to keep the full picture of what's going on.
SQLite
- Show HN: Roast my SQLite encryption at-rest
-
A SQLite extension that brings column-oriented tables to SQLite
If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.
https://github.com/sqlite/sqlite/tree/master/ext/lsm1
https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...
- SQLite License
-
Ask HN: Where do I find good code to read?
The sqlite code base is really well done. Lots of documentation.
https://github.com/sqlite/sqlite
-
Show HN: I wrote a RDBMS (SQLite clone) from scratch in pure Python
Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...
Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c
That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.
-
SQLite Begin Concurrent
Correct, see the github mirror[1]. I don't know how well supported that feature is compared to main branch. If it was completely stable, then it would have already landed in the main stable branch. Clarity about the roadmap of that branch would be nice.
1. https://github.com/sqlite/sqlite/tree/begin-concurrent
- Why sqlite3 temp files were renamed 'etilqs_*' (2006)
- SQLite builds for WASI since 3.41.0
-
SQLite VS sqlite_blaster - a user suggested alternative
2 projects | 17 Mar 2023
-
Stop Saying “Technical Debt”
Including comprehensive comments, documentation and tests in a codebase takes time and effort.
Failing to do so creates code that is very difficult to maintain or for someone new to the codebase to understand.
However, time and effort may not be what the organization wants to pay for, and individuals may view their own incomprehensible code as something like job security, as they can't be replaced by someone else easily.
As an example of complicated code that's still well-documented, the open-source sqlite code is a good example, about 1/4 of the B-tree file is comments, every time a variable is defined there's a short note explaining what it's used for, every function has a comment header that's comprehensive, such that someone new to the codebase could construct a map of how it all works fairly quickly. It's a good model for how to avoid the problem:
https://github.com/sqlite/sqlite/blob/master/src/btree.c
What are some alternatives?
workers-rs - Write Cloudflare Workers in 100% Rust via WebAssembly
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
asyncify - Standalone Asyncify helper for Binaryen
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
wasm-sqlite - [Experimental] SQLite compiled to WASM with pluggable page storage.
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
binaryen - Optimizer and compiler/toolchain library for WebAssembly
sqlite_orm - ❤️ SQLite ORM light header only library for modern C++
do-sqlite - [Experimental] Persist SQLite in a Cloudflare Durable Object
bolt
wasi-libc - WASI libc implementation for WebAssembly
phpMyAdmin - A web interface for MySQL and MariaDB