@databases VS NeDB

At Databases because you don't need ORM.

Depending on the complexity of your queries, Prisma might indeed not be the best abstraction for you. If you're proficient in SQL and don't want to sacrifice type-safety, there are really nice, low-level alternatives to Prisma such as Zapatos, Slonik or atdatabases. We're laying this out in our docs here: Should you use Prisma?

I built https://www.atdatabases.org to make this as easy as possible to get right when querying SQL databases with node.js

Depends a lot on the size of your database records. We’ve found that for a few tables with big JSONB columns it can make a huge difference but for 90% of queries it makes very little difference. https://www.atdatabases.org with @databases/pg-typed or @databases/mysql-typed also keeps the types in sync with which columns you select.

Since the method is marked as async, you can use await to get the results of a query (if your database library supports promises. For example with https://www.atdatabases.org as your db library you could do

I found Prisma close but not quite there. That's part of what motivated me to keep working on https://www.atdatabases.org, which I think is already there as an enterprise ready ORM for node.js

I built https://www.atdatabases.org which has an ORM for node.js, but also supports writing SQL queries in a safe way. It is type safe, and has much simpler & more flexible transaction support than most node.js ORMs.

If you’re using TypeScript and don’t have untrusted user data, @databases can generate static types, which can be a good alternative to runtime validation.

Did either of you consider @databases? It has pretty much the same approach to SQL as Slonik. I’m curious if there’s any reason why Slonik is preferable?

Yes! I plan to maintain it long-term! I will be rolling out some feature improvements and updates these few weeks.

I still think Kong did a good job in crafting the product. I started using Insomnia in my previous company 3 years ago and our team loved it.

What happened recently felt a little bit like the Unity fiasco (of course, in a much smaller scale). Though as a user I would say Kong had taken a bad turn, I'm still grateful to them for open-sourcing such a fantastic product.

One of the reasons I forked it was because I've read the code and I think it's quite nicely written overall (but unfortunately things like nedb that was used is no longer maintained https://github.com/louischatriot/nedb so it's probably wise to swap out at some point)

Sounds like node is trying to fsync to an unsupported file system. Top hit on goolge does not look promising: https://github.com/louischatriot/nedb/issues/407

You can pick one from this NeDB's issue that fits your needs, or keep using NeDB if it is still working for you, no longer maintained != not working.

At least for my needs, NeDB[0] is the best of both worlds for prototyping and early-stage production releases. It's human-readable, on-disk, greppable, still supports indexing and a subset of Mongo features while remaining serverless and in-memory.

[0] https://github.com/louischatriot/nedb

Local: Local specific logic. For example, code to write to a Nedb table.

What I'd do to get the best understanding of how NeDB works is to dive into the docs here. The primary things to keep in mind are that there can be other non-JSON data in those files, and that all of the document data is appended and periodically compacted, which means you'll often have an arbitrary number of duplicates and versions within the same file.

I've used https://github.com/louischatriot/nedb before but it may not meet your needs.

NeDB compatible with MongoDB

Also, there is a javascript solution called nedb: https://github.com/louischatriot/nedb, which does largely the same thing

There is similar project in Javascript called NeDB