Lowdb VS zap-db

https://github.com/typicode/lowdb is a cool option.

I just finished the first stable version of go-store, a lightweight embeeded database written in pure Go. It was heavily inspired by lowdb. The motivation was that I needed something simple to store information for another project and that I wanted to try out Go's generics.

https://jsondb.io/ or https://github.com/typicode/lowdb

By default, requests are stored locally in a JSON file with the help of LowDB.

For 1: Don't.* For 2: You're looking for a cache. I've published an OS npm module. Looking at the code might help: https://github.com/tq-bit/qache/blob/master/src/Cache.ts For 3: Maybe the code of lowdb can point you in the right direction: https://github.com/typicode/lowdb/tree/main/src

Another thing you might consider is literally using the filesystem as a database. There are plenty of vanillla ways to simply read/write to JSON or you could even use a JSON based db github.com/typicode/lowdb again you don't need to think about it as a db your just handling JS objects.

I did want something performant so that I would (hopefully) not run into issues when there are around 100-ish clients connected at the same time. I looked at low-db for a while but did not like that it would JSON.stringify my whole database on every change, which could become a problem when it becomes to big.

An easy to use JSON database written with ease of setup and memory management of slack bots in mind.

https://github.com/sdslabs/zap-db

You should consider avoiding sync FS operations however, such as in https://github.com/sdslabs/zap-db/blob/master/src/lib/session.ts . This is because of how the event loop in Node.js works: using async operations allows Node.js to work on another request while it waits for the operating system to read the file; if you use sync operations, however, it blocks the entire event loop so only one request at a time can be processed.