NeDB VS database-js

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

That I understand.

But of course for the user of the driver it might be fine if that is 2 or more HTTP requests. I expect that is how PlanetScale does it in their transaction implementation, https://github.com/planetscale/database-js#transactions, and I know that is how Prisma Data Proxy handles it - the transaction is identified with an ID which is returned to the Client and then included in further requests for the same transaction.

It's valid tradeoff to make to prefer a persistent connection to keep the overhead for multiple queries in a transaction as low as possible - which seems what Neon has done here.

The PlanetScale team recently released their database driver which lets your query your PlanetScale database using the Fetch API. This means you can use this library to query your database in edge environments which is HUGE.

> what happens if the company goes down?

It's open-source. What's your concern now?

https://github.com/planetscale/database-js