blueboat VS deploy_feedback

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....

> 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

Hey all, Andy from the Deno team here. We're excited to share with you Deno Subhosting, an easy way to extend your platforms functionality by securely running untrusted JavaScript written by your users.

When we first launched [Deno Deploy](https://deno.com/deploy) in 2021, we were surprised at the volume of requests from companies about getting access to the APIs needed to run Deno Deploy. Many companies wanted to give their users the ability to write custom logic in their app, but setting this up in the cloud presents security concerns and a ton of infra work/maintenance.

We realized that there was an opportunity for Subhosting to solve a larger problem, which is allowing companies to easily and securely run custom code written by their users, without the hassle of maintaining said infrastructure.

Though we do have a few subhosting customers (Netlify being one of them), this launch makes our Subhosting product self-service, so any development team interested in extending their platform via their users' custom code can do so by [signing up](http://dash.deno.com/subhosting/new_auto) and [reading our docs](https://docs.deno.com/deploy/manual/subhosting). We have [an updated pricing model for Subhosting](https://deno.com/deploy/pricing?subhosting) as well, including a generous free tier fit for kicking the tires and building a proof-of-concept.

We'd love to get your feed back. Have you ever talked to your co-workers about allowing external devs to "have at it" with your platform? What would it look like to unlock the final 10% for your top customers? How have you approached this problem in the past?

Thanks for reading and the Deno team will be responding to comments!

[Read the announcement blog post.](https://deno.com/blog/subhosting)

That means we don’t need to transpile the Typescript code to ESM or CJS. Currently, only Deno Deploy can run your Typescript function out of the box. However, in order to keep the code small, we still need some sort of bundling. Luckily, Bun is also a bundler 😉

What type of apps do you code for your day-job? (I program for fun and curiosity, so that is why I ask that lame question.)

Do you use node.js? Deno is brought in part by the Node.js creator, Ryan Dahl, who wanted to fix/improve a lot of things he didn't like in node.js.

They also have "Deno Deploy" (with a free tier) to run your code on different servers scattered throughout the globe: https://deno.com/deploy

One of the reasons I love the `deno` executable is you can use `import` statements in your code and then tell `deno` to merge everything into a single .js file. I would then take that and publish it to Cloudflare Workers. I know you can do this with node.js and a bunch of tools, but it is so much simpler with `deno`.

The online version of DocTrack is hosted through Deno Deploy and is accessible here.

It runs on https://deno.com/deploy which runs on gcp at the moment but my understanding is that the underlying cloud provider could change at any time.

For deployment Deno offers it's own service, Deno Deploy:

https://deno.com/deploy

Disclaimer: Haven't used it yet.

Deno functions. Its different than docker containers that auto scale. https://deno.com/deploy

One of the biggest annoyances with Deno deploy/functions is that there is no way to store any data. This would be very useful to e.g. cache an auth token, store a key/value pair, etc. See also: https://github.com/denoland/deploy_feedback/issues/110

Is any work being done to fix this? Or is this out of scope currently?

One of the valuable features of Solid Start is that you can use so-called "adapters" to completely change the output into something deployable basically everywhere that serves pages and with quite a lot of options: there are adapters for amazon web services, cloudflare pages and workers, deno deploy, netlify, standard node server (the default), vercel, and static deployment - the latter allows us to build something that we can put on github pages.