Our great sponsors
|26 days ago||9 months ago|
|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?
12 projects | news.ycombinator.com | 15 Jun 2022
Blueboat may be what you’re looking for12 projects | news.ycombinator.com | 15 Jun 2022
> 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.
Using Solid Start with GitHub pages
6 projects | dev.to | 13 Feb 2023
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.
11 projects | news.ycombinator.com | 12 Feb 2023
Developed using Fresh framework (https://fresh.deno.dev) and deployed to Deno Deploy (https://deno.com/deploy). For persistent storage I use a simple MySQL instance from DigitalOcean.
When not to use Deno ☄️
5 projects | dev.to | 5 Feb 2023
I've been really enjoying Deno for personal projects! The developer experience is excellent and Deno Deploy makes it easy to quickly & easily get things deployed.
Fast ways to build a static landing page with TS, Tailwind
2 projects | reddit.com/r/webdev | 29 Jan 2023
I really liked the ease of https://fresh.deno.dev/ and https://deno.com/deploy. Just went through the getting started guide and it was basically 'run these two commands and log in here'. But I already know react, so if that's an issue maybe choose something else.
6 projects | dev.to | 29 Dec 2022
Building a full stack app with Deno Fresh and Fauna
7 projects | dev.to | 16 Dec 2022
Fresh really takes a fresh new approach to web dev. It is still quite new but the ecosystem is rapidly growing. Up until now the Deno ecosystem was a missing a full stack framework and Fresh seems to fill that void quite effectively. You can create scalable, performant applications with Fresh and Fauna quite easily. On top of that you can make fully serverless full stack applications on the edge when you deploy your Fresh app to Deno deploy, denoflare.dev or Netlify.
Is Edge Compute Really Faster? Benchmarking Edge Platforms (With Databases)
3 projects | dev.to | 13 Dec 2022
Deno Deploy with CockroachDB
All You Need to Know About Serverless Functions and the Edge
3 projects | dev.to | 25 Nov 2022
How easy is full stack web development with Deno? 🦕- 1
4 projects | dev.to | 9 Nov 2022
8 projects | news.ycombinator.com | 27 Oct 2022
I'd say deno, because they've already established a proper ecosystem since day one, has a working usage such as Deno Deploy and Fresh, and already addresses some issues about distribution issue on Node, while bun still acts like a replacement for Node.
What are some alternatives?
miniflare - 🔥 Fully-local simulator for Cloudflare Workers
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
deno-lambda - A deno runtime for AWS Lambda. Deploy deno via docker, SAM, serverless, or bundle it yourself.
jose - "JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS for Node.js, Browser, Cloudflare Workers, Deno, Bun, and other Web-interoperable runtimes.
deno-dev-template - my deno template
wrangler-legacy - 🤠 Home to Wrangler v1 (deprecated)
fresh - The next-gen web framework.
workers-sdk - ⛅️ Home to Wrangler, the CLI for Cloudflare Workers®