NeDB VS Tile38

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... - Source: Hacker News / 7 months ago

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. - Source: Hacker News / almost 2 years ago

Local: Local specific logic. For example, code to write to a Nedb table. - Source: dev.to / almost 2 years ago

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. Source: almost 2 years ago

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

I actually worked on a project that did this. We used a database called "Tile38" [1] which used an R-Tree to make geospatial queries speedy. It was pretty good. Our dataset was ~150 GiB, I think? All in RAM. Took a while to start the server, as it all came off disk. Could have been faster. (It borrowed Redis's query language, and its storage was just "store the commands the recreate the DB, literally", IIRC. Dead... - Source: Hacker News / almost 2 years ago