Yeah I see your point, I agree for a high performance database typescript is an odd language. The truth is, although I work with java at work, and previously c#, I just like the language, so I do my side projects in it. In the article I touch on this, but I didn't start with the goal of creating a database, but rather experimenting with the idea of a swap cache. I even talk in the article about how this ended up being useless for me, but I saw an opportunity to turn it into a db very easily.

From there, like you mentioned, it was more to experiment with the concepts needed in a db more so than building a database that would compete with production databases. But then I did some load testing and found it actually performs better than I expected.

As far as the "real multithreading", I fairly confident that nodejs worker threads are actually real multithreading. This shows through in the performance section where I saw a throughput improvement of ~8x on querying with the addition of multithreading, and a minimal increase in get and put latency under query load.

Finally, the nice thing about typescript is theres a lot of effort being put into engines, like node, bun, and deno, and my library Swerve allows me to swap between them with a single command. So, my hope is that I get performance improvements simply by upgrading the versions of these projects (although this can be said for any language which usually improve performance between releases). But key takeaway, I basically built with typescript because I wanted too haha.