Dexie.js VS fastify

The word on the street is that https://github.com/rhashimoto/wa-sqlite is nearly production ready, closing in on the neat 1.0.0 release, with its IDBBatchAtomic engine highly recommended at https://www.powersync.com/blog/sqlite-persistence-on-the-web. You can try out the benchmark https://rhashimoto.github.io/wa-sqlite/demo/benchmarks.html.

And the other contestant is Dexie, stable https://dexie.org/.

If you were to branch into a new venture today, which one would you pick? And why?

That said, there are some great ways to wrap IndexedDB to make it easier to work with. Since I’m writing this article I’ll toss in my local-first framework Verdant, which can be used without the sync features as a standalone IndexedDB-powered database with a type-safe schema and deployable data migrations. For a lighter-weight approach, maybe check out Dexie.

Using IndexedDB. I have heard its pretty cumbersome to use. There are wrappers like Dexie.js but I am not sure if it works seamlessly with Tauri or if it is the correct thing for my use case.

I use IndexedDB, specifically the idb library (https://github.com/jakearchibald/idb), or Dexie.js (https://dexie.org/) if you are more novice. This works great for large sets of data. For smaller amounts, Chrome Storage API will do.

To make things easier, Dexie.js provides a straightforward and simplified process of creating databases, storing data, updating data and database migrations, etc., over the top of indexedDB.

If you are just looking for a solution for your IndexedDB needs I find Dexie to be one of the best but depending on other needs, the others in the list are also good to consider.

For example, Fastify removed the instanceof operatorfrom its codebase because it was causing problems for those developers that rely on jest as a testing framework.

Both are frameworks but NextJs is for Forntend (web app in browser that use ReactJs under the hood) and NestJs is for Backend (server app running on a server witch use Express or Fastify). The only thing similar between them is the typed language in which they were written.

Restify & Fastify Hapi

Let's create a sample Node API project we can work with throughout to build a new docker image. We will leverage Fastify to create an API that we configure via the fastify-cli.

Fastify

In setting out to build this service, we wanted to use gRPC for its APIs. We’ve been reaching for REST when building APIs so far, primarily out of necessity, i.e., our public APIs needed auto-generated client SDKs and docs for developers working with them. We built those APIs with Fastify and Typebox but felt burned by a code-first approach to generating an OpenAPI spec. I’ll spare you the details and save that experience/learning for another article. Suffice it to say we love gRPC’s schema-first approach. This blog post summarizes our feelings well

Fastify – Fast and Low overhead web framework

Custom Functions are powered by Fastify (a light-weight Node.js framework that claims to be faster than Express.js), so they’re extremely flexible.