denoify VS northwind-SQLite3

If you’re building packages/libraries for the community to use you can take a look at Denoify. It’s a project that aims to change some of your files automatically when migrating and make it easier to maintain the project for both npm and deno.land/x.

I do Node-first packages and use https://github.com/garronej/denoify to produce deno-compatible code. (example: https://github.com/mxxii/leac )

You can use https://github.com/garronej/denoify for Node-first packages.

Or use ts-patten it's comming to Deno soon (thanks to Denoify).

So, if you tried Denoify in the past and it didn't work for you, maybe it will now. If you need a hand, I'm happy to help. Just ask anything on the newly opened discussion section of the github repo.

It has zero dependencies so was very easy to dual publish on both npm and deno.land using denoify. Literally just needed to add the .ts extension to imports.

Let’s get right to the point, Bun wins. We learned earlier about its performance capabilities regarding how many requests per second it can handle, which is quite impressive. It's a similar story when it comes to database operations. Average queries per second when loading the Northwind database for SQLite using Bun’s benchmark sample are as follows:

I didnt draw this. It's included on the README of this project

I am making a sample application to improve my understanding of ASP.NET using the Northwind database for SQLite. I am using Entity Framework to interact with the database file. My question is simple. Should I be separating the data into many different DbContext classes (ProductsContext, SupplierContext, EmployeeContext, and so on...), or should I group them together somehow, or just put them all into one DataContext class. Keep in mind there is essentially only one database in this application.

I have sometimes found this one useful for demonstration purposes: SQLite version of MS Northwind

Finally, we have the SQLite benchmark. The benchmark performs a few queries on the Northwind SQLite database (which is the standard "Hello World" for SQL). Node uses better-sqlite3, Deno uses deno-sqlite, and Bun uses its built-in SQLite implementation. This benchmark seems like it is just trying to show that Bun's Zig SQLite implementation is fast, although it is a little unfair to Deno as deno-sqlite uses WASM, which often brings a performance disadvantage and therefore means that there can be faster Deno SQLite implementations.

For easy creation of sample data I have used the small version of the Northwind database available at https://github.com/jpwhite3/northwind-SQLite3.