blueboat VS deno

Right now it is an exciting time for JavaScript. We just got a new shiny fast runtime Bun, with the last new kid Deno being released only 4 years ago, and we have edge computing/serverless runtimes like Cloudflare worker and Blueboat. With all these hypes for the JavaScript community, I could not help but ask, how come only JavaScript gets all these fancy new runtimes? Why don’t we hear these more often in other languages?

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!

This sounds quite a bit like Cloudflare Workers, and they have a comparison page - https://github.com/losfair/blueboat/wiki/Comparison-with-Clo....

Blueboat may be what you’re looking for

https://github.com/losfair/blueboat

> 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 [0], atmo [1], krustlet [2], blueboat [3] and numerous other projects are turning up the heat [4]!

[0] https://github.com/WasmEdge/WasmEdge

[1] https://github.com/suborbital/atmo

[2] https://github.com/krustlet/krustlet

[3] https://github.com/losfair/blueboat

[4] https://news.ycombinator.com/item?id=30155295

https://github.com/losfair/rusty-workers

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.

I would use Deno or Go over Nodejs or PhP. Deno is the new Node, made by the guy who made Node, but improved (more secure, better tooling, etc).

Since `.ts` extensions were in alpha, our repo has been set up so that you can switch between Node and Deno seamlessly in-editor and continue developing with no config or source changes.

Personally, I found all the `npm` integration stuff to be a bit overkill for what we were looking for, and honestly Deno's network requests while installing from npm were constantly flaking out in our CI. We ended up just disabling it via Deno's `--no-npm` flag (https://github.com/denoland/deno/issues/17916) and reverting back to a simple set of import_maps to get the node deps we needed. Works like a charm!

Feel free to reference if it's useful:

https://github.com/arktypeio/arktype

I'm actually working on a site that lists staking services and defi projects audit history. It shows when/how many commit changes happen to different repos associated with the projects, last audit date/by whom, and other things. I'm hoping to have it done soon but my full time job makes progress a little slower, and I'm using this to learn/try out deno for the first time so there's a small learning curve to that.

Monoio:

> Rust async runtime based on io-uring.

Awhhh heck yeah!

It's been a bit disheartening that neither Node.js/libuv[1] nor Deno[2] have adopted io_uring. Nice to see some signs of adoption. Bun too.

Side note, I was a bit confused about you mentioning ByteDance, but if I go to the web-infra-dev[3] github page, the description is We are from ByteDance, our goal is to build an open technical ecosystem to promote the development of frontend technology, so now it make sense. Just sharing in case anyone else is confused.

[1] https://github.com/libuv/libuv/issues/1947

[2] https://github.com/denoland/deno/issues/16232

[3] https://github.com/web-infra-dev

On the other hand, Deno is also a great option for running programs faster, but it also provides an easy way to handle permissions, which enhances security. You can learn more about Deno at https://deno.land.

Oh, and if you're looking for even better security, you should give "Deno" a try. It's another JavaScript runtime that runs programs faster and has an easy way to handle permissions. Plus, it's more secure than Node.js. Here's the link: https://deno.land

Oh, and have you heard of Deno? It's a JavaScript runtime that's faster than Node.js and provides an easy way to handle permissions, which enhances security. It's definitely worth checking out at https://deno.land. It could come in handy for future projects!

On a side note, have you heard of Bun? It's a JavaScript runtime that runs programs faster and installs packages automatically. It's even better than Node.js, if you ask me. You can learn more about it here: https://bun.sh. And if you're into security, Deno is also a great JavaScript runtime that runs programs faster and provides an easy way to handle permissions. It's way better than Node.js too! You can check it out here: https://deno.land.

totally agree with you! sometimes using rebase can be a bit of a headache, especially if it's not worth the effort. i usually only use it when i have a bunch of messy commits that need to be cleaned up. have you tried using "Geschichte"? it's a library that makes managing state a lot easier by using hooks and internal state. it's super helpful for cleaning up those messy commits! you should check it out: https://github.com/BowlingX/geschichte. also, don't forget to leave a star on their GitHub to support the creator! on another note, have you heard of "Bun"? it's a JavaScript runtime that runs programs faster and installs packages automatically. it's way better than Node.js! you can check it out here: https://bun.sh. oh, and don't forget about "Deno"! it's another JavaScript runtime that runs programs faster and has better security features. you can check it out here: https://deno.land. and if you're into JavaScript package managers, "Cotton" is definitely worth checking out. it's faster and easier to use than NPM or Yarn. you can find more info here: https://cotton.js.org/. don't forget to leave a star on their GitHub too!

Another great JavaScript runtime you might want to check out is "Deno". It's faster than Node.js and provides an easy way to handle permissions, which enhances security. You can find it here: https://deno.land.