RxDB VS NeDB

I'm interested in this problem also!

I think there is a large overlap with projects that market/focus on offline-first experiences.

AFAIK this problem can be solved by:

1) Considering a client-side copy of the database that gets synced with the remote DB. This is an approach [PowerSync](https://www.powersync.com/) and [ElectricSql](https://electric-sql.com/) and [rxdb](https://rxdb.info/) take!

Hey, after I posted that, I went and gave a second look online to see if I could find something that would allow me to develop a local-first app with offline persistence and syncing capabilities.

I ended up finding some possibilities out there that could potentially help me build stuff. One of them is RxDB [1], which offers WebRTC syncing - you'd still need a signaling server, I suppose, but all sensitive information could be synced E2E-encrypted via WebRTC.

Then there's CRDT's [2], which is a universe that turned out to have multiple possibilities that match (at least partially) my needs. In particular, the next thing I want to take a look at is cr-sqlite [3], which might be just thing I needed to kick-off some side-projects.

I'm posting here cause I just found some hope of not needing to build a traditional client-server app and having to deal with all the hassle involved in securing a server (and with fear that my efforts could be not good enough), and I thought someone else could benefit from getting to know these things.

[1] https://rxdb.info/

About a year ago, I discovered a cool offline-first framework called RxDB. Initially, I thought that on the frontend side, this was exactly what I had been searching for over the past years. After tinkering around and even using it in production for some time, I realized that it wasn't well-suited for my intended use. RxDB was initially created as an RxJS layer for PouchDB with a server replication interface. Over time, other storage types besides PouchDB were introduced (e.g., IndexedDB, SQLite) and the replication interface became more sophisticated. The replication interface is really cool and exactly what I wanted. The biggest problem I have with RxDB is that it is so tightly coupled with RxJS. While RxJS is technically very powerful, it offers a dreadful developer experience. It's really hard to understand at first and integrating it into an existing codebase, which isn't using RxJS, is tedious.

Congrats to the team. Once I’ve tried https://rxdb.info/ and it wasn’t funny at all to do the remote replication (PG) and to deal with conflicts. I do need to check this out!

RxDB (Open Source but paid plugins)

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